[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250502085327.2e5be3f8@canb.auug.org.au>
Date: Fri, 2 May 2025 08:53:27 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Willy Tarreau <w@....eu>, Shuah Khan <skhan@...uxfoundation.org>, "Paul
E. McKenney" <paulmck@...nel.org>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: linux-next: Addition of the nolibc tree
Hi Thomas,
On Thu, 1 May 2025 18:30:14 +0200 Thomas Weißschuh <linux@...ssschuh.net> wrote:
>
> Hi Stephen,
>
> could you add the nolibc tree to linux-next?
> git://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git#for-next
>
> It replaces the nolibc tree from Shuah.
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git#nolibc
Done from today. I have kept the same contacts.
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