From: Stafford Horne <shorne@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Stafford Horne <shorne@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
openrisc@lists.librecores.org
Subject: Re: Add openrisc for-next branch to linux-next
Date: Thu, 1 Dec 2016 07:37:20 +0900 (JST) [thread overview]
Message-ID: <alpine.LFD.2.20.1612010735330.29569@lianli.shorne-pla.net> (raw)
In-Reply-To: <20161201083555.1b9005c2@canb.auug.org.au>
On Thu, 1 Dec 2016, Stephen Rothwell wrote:
> Hi Stafford,
>
> On Wed, 30 Nov 2016 22:22:41 +0900 (JST) Stafford Horne <shorne@gmail.com> 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
prev parent reply other threads:[~2016-11-30 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 13:22 Add openrisc for-next branch to linux-next Stafford Horne
2016-11-30 18:38 ` Randy Dunlap
2016-11-30 22:02 ` Stafford Horne
[not found] ` <CAKaYPCMpZF6tQwQrtkVMZ1+F=vSUWxAx+skyMeU6FPPA_LGgVg@mail.gmail.com>
2016-11-30 22:05 ` [OpenRISC] " Randy Dunlap
2016-11-30 22:35 ` Stafford Horne
2016-11-30 21:35 ` Stephen Rothwell
2016-11-30 22:37 ` Stafford Horne [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.20.1612010735330.29569@lianli.shorne-pla.net \
--to=shorne@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=openrisc@lists.librecores.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).