Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) client-ip=23.128.96.31;
Date:   Tue, 10 Oct 2023 15:33:54 +1100
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Shuah Khan <skhan@linuxfoundation.org>, Willy Tarreau <w@1wt.eu>,
        Thomas =?UTF-8?B?V2Vpw59zY2h1aA==?= <thomas@t-8ch.de>,
        "Paul E. McKenney" <paulmck@kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the nolibc tree
Message-ID: <20231010153354.2357ee1c@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/fLdljhEBZ4LW/Yu/a3VVNac";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/fLdljhEBZ4LW/Yu/a3VVNac
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

The following commits are also in the rcu tree as different commits
(but the same patches):

  1b831eb43176 ("tools/nolibc: string: Remove the `_nolibc_memcpy_down()` f=
unction")
  3a7296c94dfa ("tools/nolibc: x86-64: Use `rep stosb` for `memset()`")
  3f79a57865b3 ("selftests/nolibc: libc-test: avoid -Wstringop-overflow war=
nings")
  9e9dcee894f8 ("selftests/nolibc: use -nostdinc for nolibc-test")
  a04fd4052251 ("tools/nolibc: add stdarg.h header")
  ab663cc32912 ("tools/nolibc: automatically detect necessity to use pselec=
t6")
  bd216cb8d814 ("tools/nolibc: don't define new syscall number")
  c6a15707d1c3 ("tools/nolibc: string: Remove the `_nolibc_memcpy_up()` fun=
ction")
  d09e2b033a9f ("tools/nolibc: avoid unused parameter warnings for ENOSYS f=
allbacks")
  d7f2a69857ce ("MAINTAINERS: nolibc: update tree location")
  dbb6448b4263 ("selftests/nolibc: allow building i386 with multiarch compi=
ler")
  e6401064e32b ("tools/nolibc: x86-64: Use `rep movsb` for `memcpy()` and `=
memmove()`")

--=20
Cheers,
Stephen Rothwell

--Sig_/fLdljhEBZ4LW/Yu/a3VVNac
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmUk1DMACgkQAVBC80lX
0GxT8Qf/dFIcGfKYxHGeJDx4KTS4Dw+2toLuNxxwA7OfRnBGMaH1Tzn6cr8iLWGr
JsVyYrQamnfrbVPmWDixYaO5Bz7zOOKbVNkCj5nL0ZBmivgwThEu7YOOVbehE9V2
IKPVkrXNzx5d8cm9/cqFHziyDOWvDat8/FU+SThHKPd7uQZpvQ9O5kAKFxUY42Ir
z9FggyjjQbRaS4wvuzKUdx+iIdTkg7s0wDmhTJ0uAEN8fBu/IrHEqUCt5CorHySj
djIX6hiMPvhxsesgoBensxwfdLdCmVwz9iM8Y/YaA1I+OXR6UbSjY/2gOWEVQV1n
QcmlcMDZnRSj+xCr27EzfkQSAy4wEw==
=/LsU
-----END PGP SIGNATURE-----

--Sig_/fLdljhEBZ4LW/Yu/a3VVNac--