All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: linux@roeck-us.net, mark.rutland@arm.com,
	peter.maydell@linaro.org, stable@vger.kernel.org,
	will.deacon@arm.com
Subject: Re: FAILED: patch "[PATCH] arm64: kernel: fix architected PMU registers unconditional" failed to apply to 4.1-stable tree
Date: Mon, 1 Feb 2016 12:43:25 -0800	[thread overview]
Message-ID: <20160201204325.GE18440@kroah.com> (raw)
In-Reply-To: <20160201123413.GA10764@red-moon>

On Mon, Feb 01, 2016 at 12:34:13PM +0000, Lorenzo Pieralisi wrote:
> Hi Greg,
> 
> On Sun, Jan 31, 2016 at 11:17:31AM -0800, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 4.1-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>.
> 
> I will also backport a dependendency and send them to stable as a
> series.

Thanks.

> What's the standard mechanism for tagging backports (ie how do
> you prefer me stating which stable kernel version the series
> should be applied to - eg v4.1.17 ?) Usual Cc: tag or a line in
> the commit log would do ?

Either is fine, I can handle it either way.

thanks,

greg k-h

      reply	other threads:[~2016-02-01 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 19:17 FAILED: patch "[PATCH] arm64: kernel: fix architected PMU registers unconditional" failed to apply to 4.1-stable tree gregkh
2016-02-01 12:34 ` Lorenzo Pieralisi
2016-02-01 20:43   ` Greg KH [this message]

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=20160201204325.GE18440@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux@roeck-us.net \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=peter.maydell@linaro.org \
    --cc=stable@vger.kernel.org \
    --cc=will.deacon@arm.com \
    /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.