stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helmut Grohne <h.grohne@intenta.de>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] gpio: zynq: initialize clock even without CONFIG_PM" failed to apply to 4.6-stable tree
Date: Mon, 20 Jun 2016 08:22:00 +0200	[thread overview]
Message-ID: <20160620062200.GA1486@laureti-dev> (raw)
In-Reply-To: <14662680835885@kroah.com>

Hi greg,

On Sat, Jun 18, 2016 at 06:41:23PM +0200, gregkh@linuxfoundation.org wrote:
> The patch below does not apply to the 4.6-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>.

Thanks for considering the patch for stable. It seems though that my
notes concerning stable have been lost in transmission.

The first observation is that the regression was introduced in 4.4, so
no earlier stable trees are affected.

Then I had to rebase my patch, because it touches the same lines as
615d23f80efc ("gpio: zynq: Fix the error path"). My initial patch
posting[1] did not consider that patch, so there you go with a rebased
patch that applies to earlier kernel versions. I still use that patch
successfully for bisecting.

I do note however, that the mentioned "Fix the error path" commit also
looks like it should be included into a stable tree, because it fixes an
unbalanced pm_runtime_enable. Thus I recommend applying it to stable as
well. Then the patch that went into 4.7-rc3 just applies.

Helmut

[1] https://lkml.kernel.org/r/20160601110259.GA30501@laureti-dev

  reply	other threads:[~2016-06-20  6:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-18 16:41 FAILED: patch "[PATCH] gpio: zynq: initialize clock even without CONFIG_PM" failed to apply to 4.6-stable tree gregkh
2016-06-20  6:22 ` Helmut Grohne [this message]
2016-06-22  5:13   ` gregkh

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=20160620062200.GA1486@laureti-dev \
    --to=h.grohne@intenta.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linus.walleij@linaro.org \
    --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).