From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jun.zhang@intel.com, bo.he@intel.com, jie.a.bai@intel.com,
jin.xiao@intel.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt" failed to apply to 5.0-stable tree
Date: Wed, 20 Mar 2019 11:34:15 -0700 [thread overview]
Message-ID: <20190320183415.GP4102@linux.ibm.com> (raw)
In-Reply-To: <20190320182747.GA13045@kroah.com>
On Wed, Mar 20, 2019 at 07:27:47PM +0100, Greg KH wrote:
> On Wed, Mar 20, 2019 at 11:10:41AM -0700, Paul E. McKenney wrote:
> > On Wed, Mar 20, 2019 at 06:43:02PM +0100, gregkh@linuxfoundation.org wrote:
> > >
> > > The patch below does not apply to the 5.0-stable tree.
> > > If someone wants it applied there, or to any other stable or longterm
> > > tree, then please email the backport, including the original git commit
> > > id to <stable@vger.kernel.org>.
> >
> > Hello, Greg,
> >
> > "This patch does not Cc stable because it does not apply cleanly to
> > earlier kernel versions." ;-)
>
> I know, that's why I sent out these emails to remind people about it :)
Fair enough! ;-)
Thanx, Paul
> > Bo, Jin, Jie, would any of you be interested in doing the backports?
> > I would of course be happy to review them.
>
> That would be most wonderful, thanks!
>
> greg k-h
>
next prev parent reply other threads:[~2019-03-20 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 17:43 FAILED: patch "[PATCH] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt" failed to apply to 5.0-stable tree gregkh
2019-03-20 18:10 ` Paul E. McKenney
2019-03-20 18:27 ` Greg KH
2019-03-20 18:34 ` Paul E. McKenney [this message]
2019-03-21 1:21 ` He, Bo
2019-03-21 15:40 ` He, Bo
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=20190320183415.GP4102@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=bo.he@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jie.a.bai@intel.com \
--cc=jin.xiao@intel.com \
--cc=jun.zhang@intel.com \
--cc=stable@vger.kernel.org \
/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).