From: Uladzislau Rezki <urezki@gmail.com>
To: Boqun Feng <boqun.feng@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"Paul E. McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Joel Fernandes <joel@joelfernandes.org>
Subject: Re: linux-next: duplicate patch in the paulmck tree
Date: Mon, 28 Apr 2025 17:18:40 +0200 [thread overview]
Message-ID: <aA-cUPL6NZEms1ZY@pc636> (raw)
In-Reply-To: <aA-RAjmhvIbI_z9b@Mac.home>
On Mon, Apr 28, 2025 at 07:30:26AM -0700, Boqun Feng wrote:
> [Cc Joel]
>
> On Mon, Apr 28, 2025 at 06:08:45PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > The following commit is also in the rcu tree as a different commit
> > (but the same patch):
> >
> > 5c9e0062989e ("tools/memory-model/Documentation: Fix SRCU section in explanation.txt")
> >
> > This is commit
> >
> > 8e40035aab95 ("tools/memory-model/Documentation: Fix SRCU section in explanation.txt")
> >
> > in the rcu tree.
> >
>
> @Joel, should we drop this commit from rcu?
>
IMO, it should be dropped from the RCU tree as soon as it is from
another kernel part.
Paul was about to deliver this via another track. But it can be that
plans have been changed.
--
Uladzislau Rezki
next prev parent reply other threads:[~2025-04-28 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 8:08 linux-next: duplicate patch in the paulmck tree Stephen Rothwell
2025-04-28 14:30 ` Boqun Feng
2025-04-28 15:18 ` Uladzislau Rezki [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-17 7:23 Stephen Rothwell
2024-10-17 13:52 ` Paul E. McKenney
2024-08-05 4:57 Stephen Rothwell
2024-08-05 14:04 ` 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=aA-cUPL6NZEms1ZY@pc636 \
--to=urezki@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).