2023-10-10 04:34:15

by Stephen Rothwell

[permalink] [raw]
Subject: linux-next: duplicate patches in the nolibc tree

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()`")

--
Cheers,
Stephen Rothwell

Attachments:
(No filename) (499.00 B)
OpenPGP digital signature

2023-10-10 13:47:34

by Paul E. McKenney

[permalink] [raw]
Subject: Re: linux-next: duplicate patches in the nolibc tree

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

2023-10-10 13:47:40

by Thomas Weißschuh

[permalink] [raw]
Subject: Re: linux-next: duplicate patches in the nolibc tree

On 2023-10-10 06:44:00-0700, Paul E. McKenney wrote:
> 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?

Should be this one:

https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/log/?h=nolibc

Sorry for the breakage.

2023-10-10 14:04:30

by Shuah Khan

[permalink] [raw]
Subject: Re: linux-next: duplicate patches in the nolibc tree

On 10/10/23 07:46, Thomas Weißschuh wrote:
> On 2023-10-10 06:44:00-0700, Paul E. McKenney wrote:
>> 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?
>
> Should be this one:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/log/?h=nolibc
>
> Sorry for the breakage.

Sorry - I will update the tree.

thanks,
-- Shuah