Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758772AbcK3Wh0 (ORCPT ); Wed, 30 Nov 2016 17:37:26 -0500 Received: from mail-pf0-f195.google.com ([209.85.192.195]:33866 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751500AbcK3WhY (ORCPT ); Wed, 30 Nov 2016 17:37:24 -0500 From: Stafford Horne X-Google-Original-From: Stafford Horne Date: Thu, 1 Dec 2016 07:37:20 +0900 (JST) To: Stephen Rothwell cc: Stafford Horne , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, openrisc@lists.librecores.org Subject: Re: Add openrisc for-next branch to linux-next In-Reply-To: <20161201083555.1b9005c2@canb.auug.org.au> Message-ID: References: <20161201083555.1b9005c2@canb.auug.org.au> User-Agent: Alpine 2.20 (LFD 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1524 Lines: 45 On Thu, 1 Dec 2016, Stephen Rothwell wrote: > Hi Stafford, > > On Wed, 30 Nov 2016 22:22:41 +0900 (JST) Stafford Horne wrote: >> >> I have been working on getting the OpenRISC backlog of fixes sorted out >> for upstream. Can this branch be added to linux-next? >> >> git://github.com/openrisc/linux.git for-next >> >> These have been through a few reviews and we plan to ask Linus to pull in >> the next merge window. > > Added from today. > > Just a note: your top commits has no Signed-off-by from you as the committer ... Hello, Right I had been adding those as part of the `git send-email` phase but I realize I do need them in git now. Sorry about that. > Thanks for adding your subsystem tree as a participant of linux-next. As > you may know, this is not a judgement of your code. The purpose of > linux-next is for integration testing and to lower the impact of > conflicts between subsystems in the next merge window. > > You will need to ensure that the patches/commits in your tree/series have > been: > * submitted under GPL v2 (or later) and include the Contributor's > Signed-off-by, > * posted to the relevant mailing list, > * reviewed by you (or another maintainer of your subsystem tree), > * successfully unit tested, and > * destined for the current or next Linux merge window. > > Basically, this should be just what you would send to Linus (or ask him > to fetch). It is allowed to be rebased if you deem it necessary. Thank You, -Stafford