[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aA-cUPL6NZEms1ZY@pc636>
Date: Mon, 28 Apr 2025 17:18:40 +0200
From: Uladzislau Rezki <urezki@...il.com>
To: Boqun Feng <boqun.feng@...il.com>,
"Paul E. McKenney" <paulmck@...nel.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
"Paul E. McKenney" <paulmck@...nel.org>,
Frederic Weisbecker <frederic@...nel.org>,
Neeraj Upadhyay <neeraj.upadhyay@...nel.org>,
Uladzislau Rezki <urezki@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Joel Fernandes <joel@...lfernandes.org>
Subject: Re: linux-next: duplicate patch in the paulmck tree
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
Powered by blists - more mailing lists