All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: pbonzini@redhat.com, linuc.decode@gmail.com,
	torvalds@linux-foundation.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] srcu: Allow use of Classic SRCU from both process and" failed to apply to 4.9-stable tree
Date: Mon, 12 Jun 2017 21:17:34 +0200	[thread overview]
Message-ID: <20170612191734.GB2114@kroah.com> (raw)
In-Reply-To: <20170612163151.GW3721@linux.vnet.ibm.com>

On Mon, Jun 12, 2017 at 09:31:51AM -0700, Paul E. McKenney wrote:
> On Mon, Jun 12, 2017 at 02:17:59PM +0200, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 4.9-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>.
> 
> Indeed, this won't apply cleanly to 4.9 and earlier because of some
> changes to the way SRCU works.  And if you try to make the obvious
> adjustments to make the patch apply, you will break SRCU.

Oh good, I was wondering about that, I thought I had backported it
properly, but then I figured I really don't know how rcu works in
detail, so decided to just punt and reject it :)

thanks,

greg k-h

  parent reply	other threads:[~2017-06-12 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 12:17 FAILED: patch "[PATCH] srcu: Allow use of Classic SRCU from both process and" failed to apply to 4.9-stable tree gregkh
2017-06-12 16:31 ` Paul E. McKenney
2017-06-12 16:35   ` Paolo Bonzini
2017-06-12 17:21     ` Paul E. McKenney
2017-06-12 19:17   ` Greg KH [this message]
2017-06-12 20:15     ` 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=20170612191734.GB2114@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linuc.decode@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.