From: Michael Ellerman <mpe@ellerman.id.au>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: christophe.leroy@c-s.fr, joel@jms.id.au,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
srikar@linux.vnet.ibm.com, herbert@gondor.apana.org.au
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-4.19-4 tag
Date: Sat, 06 Oct 2018 22:24:28 +1000 [thread overview]
Message-ID: <87y3bbi7pf.fsf@concordia.ellerman.id.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi Greg,
Please pull some more powerpc fixes for 4.19:
The following changes since commit 7e0cf1c983b5b24426d130fd949a055d520acc9a:
selftests/powerpc: Fix Makefiles for headers_install change (2018-09-28 15:07:45 +1000)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-4.19-4
for you to fetch changes up to ac1788cc7da4ce54edcfd2e499afdb0a23d5c41d:
powerpc/numa: Skip onlining a offline node in kdump path (2018-10-05 23:21:54 +1000)
- ------------------------------------------------------------------
powerpc fixes for 4.19 #4
Four regression fixes.
A fix for a change to lib/xz which broke our zImage loader when building with XZ
compression. OK'ed by Herbert who merged the original patch.
The recent fix we did to avoid patching __init text broke some 32-bit machines,
fix that.
Our show_user_instructions() could be tricked into printing kernel memory, add a
check to avoid that.
And a fix for a change to our NUMA initialisation logic, which causes crashes in
some kdump configurations.
Thanks to:
Christophe Leroy, Hari Bathini, Jann Horn, Joel Stanley, Meelis Roos, Murilo
Opsfelder Araujo, Srikar Dronamraju.
- ------------------------------------------------------------------
Christophe Leroy (1):
powerpc/lib: fix book3s/32 boot failure due to code patching
Joel Stanley (1):
lib/xz: Put CRC32_POLY_LE in xz_private.h
Michael Ellerman (1):
powerpc: Don't print kernel instructions in show_user_instructions()
Srikar Dronamraju (1):
powerpc/numa: Skip onlining a offline node in kdump path
arch/powerpc/kernel/process.c | 10 ++++++++++
arch/powerpc/lib/code-patching.c | 20 ++++++++++++--------
arch/powerpc/mm/numa.c | 5 +++--
lib/xz/xz_crc32.c | 1 -
lib/xz/xz_private.h | 4 ++++
5 files changed, 29 insertions(+), 11 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAlu4qRMACgkQUevqPMjh
pYDEmRAAg7zDF379BIYZ9cCtyaEsPr1Qozu4qMKlq0cwhNSBNIC6AIjxlYqbRVcX
qmlvfSCfxEXxFOWLVxVxChNtYHTkRnhK0UFus6DszsJcBwxNlJCfXS8ufhOFDlpt
OKBx1bqS3NIiWhSXOzSmwHY9L4o/oyiZKjfk4HJ/7er0woS20bF3pHtXPdsuEjno
dSMftLI5YYKWSKAfsv1z6zSQRdxWOqM3Zd+Zpnvp9oTNSgqPvRFU9JwnGXVbJHOk
mQsJalMCOnbVphW8XnImbtW7TQfkbctmN95rl/OcEVm39QX4UL7suAJih5Z45TIU
mYuXXH6gTahGd4N3RfGUf2QO/3pQOiPOpywuqey/Pa68Bc5b2/fvySQ2sdMhE6yJ
rMfYlXDlFd/xL63d231QR8DiTzSdDHhDUo7T6R12fJK2f/q5Sng6rJj/71o68lun
9v/Jvt/G/Z9w25AUsPO2zlS/rIVP7C7EGknycBe5UwC2DRx7HCtKwFjOb0e2BY23
ysqF3Jpk+TsLBES4ye9vafhhDlGZg/cuej0OWFf0Ca/bi1fV59Hw2XaI3qj+VsFf
psl/DcJE8+EyDUVAVloYaM8yr96QJdH7+I9Ea/8FC4cyJSIAiMzrlrTp/zonzbQl
hbMVjZujVrQiNdbJ+irb7bCpaAPXdP81CK4FSGGyRvJ0Jycnvno=
=u2T9
-----END PGP SIGNATURE-----
next reply other threads:[~2018-10-06 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 12:24 Michael Ellerman [this message]
2018-10-07 5:21 ` 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=87y3bbi7pf.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@c-s.fr \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=srikar@linux.vnet.ibm.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
all inboxes | Powered by JetHome®