* linux-next: duplicate patches in the nolibc tree
@ 2023-10-10 4:33 Stephen Rothwell
2023-10-10 13:44 ` Paul E. McKenney
0 siblings, 1 reply; 4+ messages in thread
From: Stephen Rothwell @ 2023-10-10 4:33 UTC (permalink / raw)
To: Shuah Khan, Willy Tarreau, Thomas Weißschuh,
Paul E. McKenney
Cc: Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: linux-next: duplicate patches in the nolibc tree
2023-10-10 4:33 linux-next: duplicate patches in the nolibc tree Stephen Rothwell
@ 2023-10-10 13:44 ` Paul E. McKenney
2023-10-10 13:46 ` Thomas Weißschuh
0 siblings, 1 reply; 4+ messages in thread
From: Paul E. McKenney @ 2023-10-10 13:44 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Shuah Khan, Willy Tarreau, Thomas Weißschuh,
Linux Kernel Mailing List, Linux Next Mailing List
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
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: linux-next: duplicate patches in the nolibc tree
2023-10-10 13:44 ` Paul E. McKenney
@ 2023-10-10 13:46 ` Thomas Weißschuh
2023-10-10 14:04 ` Shuah Khan
0 siblings, 1 reply; 4+ messages in thread
From: Thomas Weißschuh @ 2023-10-10 13:46 UTC (permalink / raw)
To: Paul E. McKenney
Cc: Stephen Rothwell, Shuah Khan, Willy Tarreau,
Linux Kernel Mailing List, Linux Next Mailing List
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.
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: linux-next: duplicate patches in the nolibc tree
2023-10-10 13:46 ` Thomas Weißschuh
@ 2023-10-10 14:04 ` Shuah Khan
0 siblings, 0 replies; 4+ messages in thread
From: Shuah Khan @ 2023-10-10 14:04 UTC (permalink / raw)
To: Thomas Weißschuh, Paul E. McKenney
Cc: Stephen Rothwell, Willy Tarreau, Linux Kernel Mailing List,
Linux Next Mailing List, Shuah Khan
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-10-10 14:04 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-10-10 4:33 linux-next: duplicate patches in the nolibc tree Stephen Rothwell
2023-10-10 13:44 ` Paul E. McKenney
2023-10-10 13:46 ` Thomas Weißschuh
2023-10-10 14:04 ` Shuah Khan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox