[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210714084106.0525b879@canb.auug.org.au>
Date: Wed, 14 Jul 2021 08:41:06 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Jul 13
Hi Geert,
On Tue, 13 Jul 2021 10:44:40 +0200 Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>
> I've just noticed you don't have
>
> renesas-fixes git
> git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git#fixes
>
> included yet. Can you please add it?
> This branch contains fixes intended for the current release.
Added from today.
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