All of lore.kernel.org
 help / color / mirror / Atom feed
From: "He, Bo" <bo.he@intel.com>
To: "paulmck@linux.ibm.com" <paulmck@linux.ibm.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: "Zhang, Jun" <jun.zhang@intel.com>,
	"Bai, Jie A" <jie.a.bai@intel.com>,
	"Xiao, Jin" <jin.xiao@intel.com>,
	"stable@vger.kernel.org" <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: Thu, 21 Mar 2019 01:21:46 +0000	[thread overview]
Message-ID: <CD6925E8781EFD4D8E11882D20FC406D52A639EC@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20190320183415.GP4102@linux.ibm.com>

sure, we have backported the patch to lts4.19 in intel local branch, and will also send out the backport patches for other LTS.

-----Original Message-----
From: Paul E. McKenney <paulmck@linux.ibm.com> 
Sent: Thursday, March 21, 2019 2:34 AM
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Zhang, Jun <jun.zhang@intel.com>; He, Bo <bo.he@intel.com>; Bai, Jie A <jie.a.bai@intel.com>; Xiao, Jin <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

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
> 


  reply	other threads:[~2019-03-21  1:21 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
2019-03-21  1:21       ` He, Bo [this message]
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=CD6925E8781EFD4D8E11882D20FC406D52A639EC@SHSMSX104.ccr.corp.intel.com \
    --to=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=paulmck@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.