From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [stable:PATCH 0/3] PAN fixes backport for v4.4.35
Date: Fri, 2 Dec 2016 16:42:44 +0000 [thread overview]
Message-ID: <20161202164247.19496-1-james.morse@arm.com> (raw)
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
Patch 1 changes the prototype of all the feature/errata enable calls, so
is fiddly to backport, hence doing it later as a separate series.
Patch 3 has had the UAO desription removed from its commit message as
v4.4 doesn't support this feature.
Thanks,
James Morse (3):
arm64: cpufeature: Schedule enable() calls instead of calling them via
IPI [v4.4]
arm64: mm: Set PSTATE.PAN from the cpu_enable_pan() call [v4.4]
arm64: suspend: Reconfigure PSTATE after resume from idle [v4.4]
arch/arm64/include/asm/cpufeature.h | 2 +-
arch/arm64/include/asm/processor.h | 2 +-
arch/arm64/kernel/cpufeature.c | 10 +++++++++-
arch/arm64/kernel/suspend.c | 9 +++++++++
arch/arm64/mm/fault.c | 12 +++++++++++-
5 files changed, 31 insertions(+), 4 deletions(-)
--
2.10.1
next reply other threads:[~2016-12-02 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 16:42 James Morse [this message]
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
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=20161202164247.19496-1-james.morse@arm.com \
--to=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).