Re: linux-next: duplicate patches in the nolibc tree

[Paul E. McKenney]

On Tue, Oct 10, 2023 at 03:33:54PM +1100, Stephen Rothwell wrote:
> 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()` function")
>   3a7296c94dfa ("tools/nolibc: x86-64: Use `rep stosb` for `memset()`")
>   3f79a57865b3 ("selftests/nolibc: libc-test: avoid -Wstringop-overflow warnings")
>   9e9dcee894f8 ("selftests/nolibc: use -nostdinc for nolibc-test")
>   a04fd4052251 ("tools/nolibc: add stdarg.h header")
>   ab663cc32912 ("tools/nolibc: automatically detect necessity to use pselect6")
>   bd216cb8d814 ("tools/nolibc: don't define new syscall number")
>   c6a15707d1c3 ("tools/nolibc: string: Remove the `_nolibc_memcpy_up()` function")
>   d09e2b033a9f ("tools/nolibc: avoid unused parameter warnings for ENOSYS fallbacks")
>   d7f2a69857ce ("MAINTAINERS: nolibc: update tree location")
>   dbb6448b4263 ("selftests/nolibc: allow building i386 with multiarch compiler")
>   e6401064e32b ("tools/nolibc: x86-64: Use `rep movsb` for `memcpy()` and `memmove()`")

Apologies for the hassle, but which is the non-rcu tree?

							Thanx, Paul