From: Willy Tarreau <w@1wt•eu>
To: Randy Dunlap <rdunlap@infradead•org>
Cc: Shuah Khan <skhan@linuxfoundation•org>,
linux-next@vger•kernel.org,
Stephen Rothwell <sfr@canb•auug.org.au>,
"Paul E. McKenney" <paulmck@kernel•org>,
thomas@t-8ch•de, linux-kernel@vger•kernel.org,
shuah <shuah@kernel•org>
Subject: Re: Request for linux-kselftest nolibc branch Inclusion in linux-next
Date: Thu, 27 Jul 2023 05:25:58 +0200 [thread overview]
Message-ID: <20230727032558.GA27996@1wt.eu> (raw)
In-Reply-To: <f28bfb83-49c6-53b1-71db-aba815505af4@infradead.org>
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 - 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>
>
> 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
prev parent reply other threads:[~2023-07-27 3:29 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
2023-07-26 23:17 ` Randy Dunlap
2023-07-27 3:25 ` Willy Tarreau [this message]
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=20230727032558.GA27996@1wt.eu \
--to=w@1wt$(echo .)eu \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paulmck@kernel$(echo .)org \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=shuah@kernel$(echo .)org \
--cc=skhan@linuxfoundation$(echo .)org \
--cc=thomas@t-8ch$(echo .)de \
/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