From: Greg KH <gregkh@linuxfoundation.org>
To: James Morse <james.morse@arm.com>
Cc: stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [stable:PATCH 0/3] PAN fixes backport for v4.4.35
Date: Mon, 5 Dec 2016 13:44:53 +0100 [thread overview]
Message-ID: <20161205124453.GA18874@kroah.com> (raw)
In-Reply-To: <584538CC.50807@arm.com>
On Mon, Dec 05, 2016 at 09:52:12AM +0000, James Morse wrote:
> Hi Greg,
>
> On 02/12/16 17:23, Greg KH wrote:
> > On Fri, Dec 02, 2016 at 04:42:44PM +0000, James Morse wrote:
> >> Hi linux-stable,
> >>
> >> This is the backport of the recent PAN fixes series for v4.4.35.
> >> Original series:
> >> http://lists.infradead.org/pipermail/linux-arm-kernel/2016-October/461806.html
> >
> > Why just 4.4-stable? What about 4.8-stable?
>
> Patch 1 doesn't backport easily. I was going to do v4.8 next, but thought one at
> a time would be the least confusing...
>
> (I don't seem to be very good at predicting what is confusing!)
Adding a patch to an "old" stable kernel would be odd if the latest
stable kernel also doesn't have it, right? I need for it to be in 4.8
before I can take it into 4.4, sorry.
So I'll hold off on applying these until that happens.
thanks,
greg k-h
next prev parent reply other threads:[~2016-12-05 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 16:42 [stable:PATCH 0/3] PAN fixes backport for v4.4.35 James Morse
2016-12-02 16:42 ` [stable:PATCH 1/3] arm64: cpufeature: Schedule enable() calls instead of calling them via IPI [v4.4] James Morse
2016-12-02 16:42 ` [stable:PATCH 2/3] arm64: mm: Set PSTATE.PAN from the cpu_enable_pan() call [v4.4] James Morse
2016-12-02 16:42 ` [stable:PATCH 3/3] arm64: suspend: Reconfigure PSTATE after resume from idle [v4.4] James Morse
2016-12-02 17:23 ` [stable:PATCH 0/3] PAN fixes backport for v4.4.35 Greg KH
2016-12-05 9:52 ` James Morse
2016-12-05 12:44 ` Greg KH [this message]
2016-12-06 20:24 ` Greg KH
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=20161205124453.GA18874@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).