Hi Stephen,
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 - [email protected] or Shuah Khan <[email protected]>
Please cc:
Willy Tarreau <[email protected]>
Thomas Weißschuh <[email protected]>
Paul E. McKenney <[email protected]>
thanks,
-- Shuah
Hi Shuah,
On Mon, 24 Jul 2023 16:22:16 -0600 Shuah Khan <[email protected]> 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 - [email protected] or Shuah Khan <[email protected]>
>
> Please cc:
> Willy Tarreau <[email protected]>
> Thomas Weißschuh <[email protected]>
> Paul E. McKenney <[email protected]>
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
[email protected]
On 7/24/23 15:22, Shuah Khan wrote:
> Hi Stephen,
>
> 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 - [email protected] or Shuah Khan <[email protected]>
>
> Please cc:
> Willy Tarreau <[email protected]>
> Thomas Weißschuh <[email protected]>
> Paul E. McKenney <[email protected]>
Should the MAINTAINERS file entry for NOLIBC be updated?
(I think so.)
thanks.
--
~Randy
Hi Randy,
On Wed, Jul 26, 2023 at 04:17:41PM -0700, Randy Dunlap wrote:
>
>
> On 7/24/23 15:22, Shuah Khan wrote:
> > Hi Stephen,
> >
> > 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 - [email protected] or Shuah Khan <[email protected]>
> >
> > Please cc:
> > Willy Tarreau <[email protected]>
> > Thomas Wei?schuh <[email protected]>
> > Paul E. McKenney <[email protected]>
>
> Should the MAINTAINERS file entry for NOLIBC be updated?
> (I think so.)
Yes we planned to do it and will do it soon.
Thanks,
Willy