Hi Shuah, On Mon, 24 Jul 2023 16:22:16 -0600 Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx> wrote: > > Please include the following linux-kselftest nolibc branch for linux-next > coverage. This will be based on Linus's tree. > > I will be using this branch to send nolibc pull requests to Linus. > > URL for the branch: > https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/log/?h=nolibc > > Primary Contacts: > Shuah Khan - shuah@xxxxxxxxxx or Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx> > > Please cc: > Willy Tarreau <w@xxxxxx> > Thomas Weißschuh <thomas@xxxxxxxx> > Paul E. McKenney <paulmck@xxxxxxxxxx> 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@xxxxxxxxxxxxxxxx
Attachment:
pgp3NuG0294ls.pgp
Description: OpenPGP digital signature
