From: "Paul E. McKenney" <paulmck@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Networking <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the rcu tree
Date: Fri, 14 Jul 2023 08:03:36 -0700 [thread overview]
Message-ID: <f8f3ed8c-66c1-4a07-8fe8-f7bb997a7dcf@paulmck-laptop> (raw)
In-Reply-To: <CAADnVQLF0BP-_Fjxi1S-0Shus38vAVdNbB2JHsBd6_RudYWF0A@mail.gmail.com>
On Thu, Jul 13, 2023 at 11:04:11PM -0700, Alexei Starovoitov wrote:
> On Thu, Jul 13, 2023 at 9:50 PM Paul E. McKenney <paulmck@kernel.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.
Very good, it goes on my next rebase later today, Pacific Time.
Thanx, Paul
next prev parent reply other threads:[~2023-07-14 15:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 4:43 linux-next: duplicate patch in the rcu tree 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 [this message]
-- 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-05-10 23:00 Stephen Rothwell
2023-05-11 16:52 ` Paul E. McKenney
2023-05-15 19:28 ` Shuah Khan
2023-05-16 12:19 ` Paul E. McKenney
2023-05-17 16:12 ` Shuah Khan
2023-05-17 17:07 ` 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=f8f3ed8c-66c1-4a07-8fe8-f7bb997a7dcf@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.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).