[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAADnVQLF0BP-_Fjxi1S-0Shus38vAVdNbB2JHsBd6_RudYWF0A@mail.gmail.com>
Date: Thu, 13 Jul 2023 23:04:11 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Networking <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the rcu tree
On Thu, Jul 13, 2023 at 9:50 PM Paul E. McKenney <paulmck@...nel.org> wrote:
>
> On Fri, Jul 14, 2023 at 02:43:30PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > The following commit is also in net-next tree as a different commit
> > (but the same patch):
> >
> > a2b38823280d ("rcu: Export rcu_request_urgent_qs_task()")
> >
> > This is commit
> >
> > 43a89baecfe2 ("rcu: Export rcu_request_urgent_qs_task()")
> >
> > in the net-next tree.
>
> The net-next tree needs it for BPF, correct?
yes.
> So if you guys intend to
> push it to mainline, I will be happy to drop if from -rcu.
That's the intent. Please drop it from -rcu.
Thank you!
Powered by blists - more mailing lists