From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Shuah Khan <skhan@linuxfoundation.org>, Willy Tarreau <w@1wt.eu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the nolibc tree
Date: Tue, 10 Oct 2023 15:46:54 +0200 [thread overview]
Message-ID: <92d99a63-876e-4d9c-be59-703b7f298c24@t-8ch.de> (raw)
In-Reply-To: <0e0f5e19-c962-458a-b52d-0aa540301c34@paulmck-laptop>
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.
next prev parent reply other threads:[~2023-10-10 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 4:33 Stephen Rothwell
2023-10-10 13:44 ` Paul E. McKenney
2023-10-10 13:46 ` Thomas Weißschuh [this message]
2023-10-10 14:04 ` Shuah Khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92d99a63-876e-4d9c-be59-703b7f298c24@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=skhan@linuxfoundation.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®