Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Sat, 22 Jul 2023 13:01:20 +1000
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 =?UTF-8?B?V2Vp?= =?UTF-8?B?w59zY2h1aA==?= 
        <thomas@t-8ch.de>, linux-kernel@vger.kernel.org
Subject: Re: Upcoming nolibc pull request for the next merge window
Message-ID: <20230722130120.6e4c0eab@canb.auug.org.au>
In-Reply-To: <7afafb6c-9664-44a1-bc8f-d20239db1dd5@paulmck-laptop>
References: <7afafb6c-9664-44a1-bc8f-d20239db1dd5@paulmck-laptop>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/f6xPJD0E9.JEJSA=IOUah=V";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/f6xPJD0E9.JEJSA=IOUah=V
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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.
>=20
> Similarly, Thomas Wei=C3=9Fschuh will be joining Willy as technical maint=
ainer
> 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?

--=20
Cheers,
Stephen Rothwell

--Sig_/f6xPJD0E9.JEJSA=IOUah=V
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmS7RoAACgkQAVBC80lX
0GwEpQf8DGSNxYOqncvhe6TSjmTRwRchkHVoZw5f3p7/oLvX2+669rLWjWca8KeN
nT89melFYeW51AwPeKiWuHl3tbYfPh2+0rl9izRvdQrR69lv9Zo6qJN7a37FlA2k
8IDrs5A1444p6co6cFSc56jmWOPsby9Es2sc0tFDpi9HWIXgyp3UpCcrr94Y3Nzw
Ki893QVUDwFXec0J0MzG5fsiYtY95ygbuhp6hGq0YO1v9W2JiWFA3wrUiyiTXBl9
epb35Hfw/uGpvgvBZX3/R1p78qBJCLUygbsB4jCBzVBswNNFYN3MBShpHUzHmmAE
pf4uFIBaij7z68H5CiCzsmP9K1MXHw==
=laiU
-----END PGP SIGNATURE-----

--Sig_/f6xPJD0E9.JEJSA=IOUah=V--