[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190812072659.606b2107@canb.auug.org.au>
Date: Mon, 12 Aug 2019 07:26:59 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Add SPDX kernel tree to linux-next
Hi Greg,
On Sat, 10 Aug 2019 13:55:33 +0200 Greg KH <gregkh@...uxfoundation.org> wrote:
>
> I realized that I've been sending patches to Linus from my "SPDX" kernel
> tree for a few releases now, and it's not included in linux-next, which
> is not good.
>
> So, could you please add the kernel tree / branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/spdx.git spdx-linus
>
> to linux-next?
Added from today. One question: is this meant to be a -next tree or a
-fixes tree?
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@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists