From: Shuah Khan <skhan@linuxfoundation•org>
To: paulmck@kernel•org, Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Shuah Khan <shuah@kernel•org>, Mark Brown <broonie@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Shuah Khan <skhan@linuxfoundation•org>
Subject: Re: linux-next: duplicate patch in the rcu tree
Date: Mon, 15 May 2023 13:28:23 -0600 [thread overview]
Message-ID: <96c6fdf7-e589-ca56-9314-1d437b8082ac@linuxfoundation.org> (raw)
In-Reply-To: <59c2fd36-6920-47d8-a79c-9ff3fcf7c7ae@paulmck-laptop>
On 5/11/23 10:52, Paul E. McKenney wrote:
> On Thu, May 11, 2023 at 09:00:10AM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> The following commit is also in the kselftest-fixes tree as a different
>> commit (but the same patch):
>>
>> 6d9ed63d8bc3 ("tools/nolibc: Fix build of stdio.h due to header ordering")
>>
>> This is commit
>>
>> d7eafa64a158 ("tools/nolibc: Fix build of stdio.h due to header ordering")
>>
>> in the kselftest-fixes tree.
>
> I can currently cleanly remove this commit from the rest of the nolibc
> commits in -rcu.
>
> However, I might need to re-introduce it in some way or another, for
> example, if there are dependencies on it by future nolibc patches.
> (I expect another batch in a few days.)
>
> So how would you like to proceed?
>
Paul,
I can drop this from linux-kselftest fixes if that is the easier path.
Just let me know.
thanks,
-- Shuah
next prev parent reply other threads:[~2023-05-15 19:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 23:00 linux-next: duplicate patch in the rcu tree Stephen Rothwell
2023-05-11 16:52 ` Paul E. McKenney
2023-05-15 19:28 ` Shuah Khan [this message]
2023-05-16 12:19 ` Paul E. McKenney
2023-05-17 16:12 ` Shuah Khan
2023-05-17 17:07 ` Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2025-06-22 21:52 Stephen Rothwell
2024-08-12 2:51 Stephen Rothwell
2024-02-28 1:06 Stephen Rothwell
2024-02-28 1:17 ` Thomas Gleixner
2024-02-28 1:26 ` Paul E. McKenney
2024-02-28 1:20 ` Paul E. McKenney
2023-11-01 1:01 Stephen Rothwell
2023-11-01 19:17 ` Paul E. McKenney
2023-10-13 4:37 Stephen Rothwell
2023-10-13 13:32 ` Paul E. McKenney
2023-07-14 4:43 Stephen Rothwell
2023-07-14 4:50 ` Paul E. McKenney
2023-07-14 6:04 ` Alexei Starovoitov
2023-07-14 15:03 ` Paul E. McKenney
2023-03-23 3:47 Stephen Rothwell
2023-03-23 3:44 Stephen Rothwell
2023-03-23 5:11 ` Paul E. McKenney
2023-03-23 19:41 ` Andrew Morton
2023-03-23 21:03 ` Paul E. McKenney
2023-01-16 1:38 Stephen Rothwell
2023-01-16 4:44 ` Paul E. McKenney
2023-01-08 23:11 Stephen Rothwell
2023-01-09 4:36 ` Paul E. McKenney
2023-01-16 1:31 ` Stephen Rothwell
2023-01-16 4:41 ` Paul E. McKenney
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=96c6fdf7-e589-ca56-9314-1d437b8082ac@linuxfoundation.org \
--to=skhan@linuxfoundation$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paulmck@kernel$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=shuah@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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