From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
npiggin@gmail.com, ravi.bangoria@linux.vnet.ibm.com
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-4.11-8 tag
Date: Fri, 21 Apr 2017 14:51:09 +1000 [thread overview]
Message-ID: <87a87a4b42.fsf@concordia.ellerman.id.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
Hi Linus,
Please pull two final powerpc fixes for 4.11:
The following changes since commit 4749228f022893faf54a3dbc70796f78b7d4f342:
powerpc/crypto/crc32c-vpmsum: Fix missing preempt_disable() (2017-04-07 21:12:58 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-4.11-8
for you to fetch changes up to be5c5e843c4afa1c8397cb740b6032bd4142f32d:
powerpc/64: Fix HMI exception on LE with CONFIG_RELOCATABLE=y (2017-04-18 20:19:52 +1000)
----------------------------------------------------------------
powerpc fixes for 4.11 #8
Just two fixes. The first fixes kprobing a stdu, and is marked for stable as
it's been broken for ~ever. In hindsight this could have gone in next.
The other is a fix for a change we merged this cycle, where if we take a certain
exception when the kernel is running relocated (currently only used for kdump),
we checkstop the box.
Thanks to:
Ravi Bangoria.
----------------------------------------------------------------
Michael Ellerman (1):
powerpc/64: Fix HMI exception on LE with CONFIG_RELOCATABLE=y
Ravi Bangoria (1):
powerpc/kprobe: Fix oops when kprobed on 'stdu' instruction
arch/powerpc/include/asm/exception-64s.h | 8 ++++----
arch/powerpc/kernel/entry_64.S | 6 +++---
arch/powerpc/kernel/exceptions-64s.S | 2 +-
3 files changed, 8 insertions(+), 8 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
reply other threads:[~2017-04-21 4:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87a87a4b42.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=ravi.bangoria@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®