mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Willy Tarreau" <w@1wt.eu>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	"Thomas Weißschuh" <thomas@t-8ch.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Upcoming nolibc pull request for the next merge window
Date: Sat, 22 Jul 2023 13:01:20 +1000	[thread overview]
Message-ID: <20230722130120.6e4c0eab@canb.auug.org.au> (raw)
In-Reply-To: <7afafb6c-9664-44a1-bc8f-d20239db1dd5@paulmck-laptop>

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

Hi Paul,

On Fri, 21 Jul 2023 10:39:48 -0700 "Paul E. McKenney" <paulmck@kernel.org> wrote:
>
> This is just to let you know that Willy and I are adding co-maintainers
> for nolibc.  Shuah Khan will join me as administrative maintainer,
> and will be sending the pull request to you for the next merge window.
> 
> Similarly, Thomas Weißschuh will be joining Willy as technical maintainer
> for nolibc.  With luck, this won't affect you, but in case you come across
> a nolibc issue, please reach out to Thomas as well as Willy, Shuah,
> and myself.  There will of course be an update to the MAINTAINERS file
> in the near future, but just to let you know in the meantime.

Would it make sense to add a separate nolibc branch to linux-next (and
no longer merge it into the rcu branch?  Or are there dependencies
between the two?

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-07-22  3:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 17:39 Paul E. McKenney
2023-07-22  3:01 ` Stephen Rothwell [this message]
2023-07-22  4:48   ` Paul E. McKenney
2023-07-24 14:49     ` Shuah Khan
2023-07-24 15:31       ` Paul E. McKenney
2023-07-24 15:37         ` Shuah Khan
2023-07-24 21:42           ` Stephen Rothwell

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=20230722130120.6e4c0eab@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=thomas@t-8ch.de \
    --cc=torvalds@linux-foundation.org \
    --cc=w@1wt.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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

all inboxes | Powered by JetHome®