From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Shuah Khan <skhan@linuxfoundation•org>
Cc: linux-next@vger•kernel.org,
"Paul E. McKenney" <paulmck@kernel•org>, Willy Tarreau <w@1wt•eu>,
thomas@t-8ch•de, linux-kernel@vger•kernel.org,
shuah <shuah@kernel•org>,
Linus Torvalds <torvalds@linux-foundation•org>
Subject: Re: Request for linux-kselftest nolibc branch Inclusion in linux-next
Date: Tue, 25 Jul 2023 09:42:19 +1000 [thread overview]
Message-ID: <20230725094219.7c1790fa@canb.auug.org.au> (raw)
In-Reply-To: <4a007283-be03-907a-094f-6651a44e631f@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
Hi Shuah,
On Mon, 24 Jul 2023 16:22:16 -0600 Shuah Khan <skhan@linuxfoundation•org> 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@kernel•org or Shuah Khan <skhan@linuxfoundation•org>
>
> Please cc:
> Willy Tarreau <w@1wt•eu>
> Thomas Weißschuh <thomas@t-8ch•de>
> Paul E. McKenney <paulmck@kernel•org>
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@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-24 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 22:22 Request for linux-kselftest nolibc branch Inclusion in linux-next Shuah Khan
2023-07-24 23:42 ` Stephen Rothwell [this message]
2023-07-26 23:17 ` Randy Dunlap
2023-07-27 3:25 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230725094219.7c1790fa@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paulmck@kernel$(echo .)org \
--cc=shuah@kernel$(echo .)org \
--cc=skhan@linuxfoundation$(echo .)org \
--cc=thomas@t-8ch$(echo .)de \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=w@1wt$(echo .)eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox