Re: Pull Request for linux-next

[Stephen Rothwell <sfr@canb.auug.org.au>]

Hi Palmer,

On Tue, 31 Oct 2017 13:43:26 -0700 (PDT) Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> I'd like to request that you add the following tree to linux-next
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git for-linux-next
> 
> It contains the RISC-V port, which has been through 9 rounds of review on
> various public Linux mailing lists.  While the port isn't perfect, I've split
> out the commits for which we have general consensus and tagged them with
> "for-linux-next" (as opposed to our "riscv-next" tree).  I intend to continue
> updating the "for-linux-next" tag as we get more patches in good shape, with
> the idea being that the RISC-V arch port patches go in through here.
> 
> I know it's a bit late in the cycle, but we've been waiting for you to come
> back from vacation before submitting the request so it didn't get lost
> somewhere.

Added from today as the risc-v tree with just you as the contact (I can
add other contacts if you want - they will be informed of conflicts and
build problems).

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.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au