stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hanjun Guo <guohanjun@huawei.com>
To: <gregkh@linuxfoundation.org>, <stable@vger.kernel.org>
Cc: <will.deacon@arm.com>
Subject: [PATCH 0/3] Candidate ARM64 stable patches for linux-4.1.y
Date: Tue, 2 Feb 2016 12:06:44 +0800	[thread overview]
Message-ID: <1454386007-11860-1-git-send-email-guohanjun@huawei.com> (raw)

From: Hanjun Guo <hanjun.guo@linaro.org>

Hi Greg,

Here are 3 candidate patches for stable linux-4.1.y, patch 2
alredy Cc stable in the change log, but need patch 1 (which
also a bugfix) to apply patch 2 cleanly, the last one is worth
to take as a bugfix too I think, please consider to merge :)

Thanks
Hanjun

Josh Stone (1):
  arm64: fix missing syscall trace exit

Will Deacon (2):
  arm64: entry: always restore x0 from the stack on syscall return
  arm64: mm: ensure patched kernel text is fetched from PoU

 arch/arm64/kernel/entry.S | 22 +++++++++++-----------
 arch/arm64/kernel/head.S  |  8 ++++++++
 arch/arm64/kernel/sleep.S |  8 ++++++++
 arch/arm64/mm/proc.S      |  1 -
 4 files changed, 27 insertions(+), 12 deletions(-)

-- 
1.9.1



             reply	other threads:[~2016-02-02  4:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02  4:06 Hanjun Guo [this message]
2016-02-02  4:06 ` [PATCH 1/3] arm64: fix missing syscall trace exit Hanjun Guo
2016-02-02  4:06 ` [PATCH 2/3] arm64: entry: always restore x0 from the stack on syscall return Hanjun Guo
2016-02-02  4:06 ` [PATCH 3/3] arm64: mm: ensure patched kernel text is fetched from PoU Hanjun Guo
2016-02-14 21:00   ` Greg KH
2016-02-15  1:43     ` Hanjun Guo
2016-02-14 21:00 ` [PATCH 0/3] Candidate ARM64 stable patches for linux-4.1.y Greg KH
2016-02-15  1:35   ` Hanjun Guo
2016-02-15  1:44     ` Greg KH
2016-02-16  5:59       ` Hanjun Guo
2016-02-16  6:09         ` Sasha Levin

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=1454386007-11860-1-git-send-email-guohanjun@huawei.com \
    --to=guohanjun@huawei.com \
    --cc=gregkh@linuxfoundation.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 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).