From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ego@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, mahesh@linux.vnet.ibm.com
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-5.1-4 tag
Date: Sun, 31 Mar 2019 21:26:08 +1100 [thread overview]
Message-ID: <87pnq7l4qn.fsf@concordia.ellerman.id.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Linus,
Please pull some more powerpc fixes for 5.1:
The following changes since commit 8c2ffd9174779014c3fe1f96d9dc3641d9175f00:
Linux 5.1-rc2 (2019-03-24 14:02:26 -0700)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-5.1-4
for you to fetch changes up to 6f845ebec2706841d15831fab3ffffcfd9e676fa:
powerpc/pseries/mce: Fix misleading print for TLB mutlihit (2019-03-29 16:59:19 +1100)
- ------------------------------------------------------------------
powerpc fixes for 5.1 #4
Three non-regression fixes.
Our optimised memcmp could read past the end of one of the buffers and
potentially trigger a page fault leading to an oops.
Some of our code to read energy management data on PowerVM had an endian bug
leading to bogus results.
When reporting a machine check exception we incorrectly reported TLB multihits
as D-Cache multhits due to a missing entry in the array of causes.
Thanks to:
Chandan Rajendra, Gautham R. Shenoy, Mahesh Salgaonkar, Segher Boessenkool,
Vaidyanathan Srinivasan.
- ------------------------------------------------------------------
Gautham R. Shenoy (1):
powerpc/pseries/energy: Use OF accessor functions to read ibm,drc-indexes
Mahesh Salgaonkar (1):
powerpc/pseries/mce: Fix misleading print for TLB mutlihit
Michael Ellerman (1):
powerpc/64: Fix memcmp reading past the end of src/dest
arch/powerpc/lib/memcmp_64.S | 17 ++++++++++++----
arch/powerpc/platforms/pseries/pseries_energy.c | 27 ++++++++++++++++---------
arch/powerpc/platforms/pseries/ras.c | 1 +
3 files changed, 32 insertions(+), 13 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIcBAEBAgAGBQJcoJWZAAoJEFHr6jzI4aWAM9sQAKzbaBFGhm+08w75Cz36I5zo
3gWG24Zzj7r2/wZfSaKIRSIKm1UvNjmhDWiQprkgVsQOScSwxfnwE9lkrGfGCFX8
eiIzNJFnCOg1ZBLfJFh/9yzWwfHiR57IqcN4lD8oAMLYVHR7JKJjA5vfTt8JxtUn
Z58im6uLgSdMnwvSJ3Wg5Oq4SX88cLsCUyQ9Mm5X0HY4LUrxboN6ofQkUj4AH55V
RG3+Z5WKoK0vQEkUrRREHpmjMB2e/fdaMULEjCLnAErU3Ip2Ku6nKZMHH3pZMC6Q
2yi2bMwXdWK9CH3lW7Q88EIGI7MYixLpLdxTedcqSI6meZaGaHAQJJEQySriPOt4
ArN5nfcfewDU9G+aT9up8JcdbBBJDvJ/ZKngPpZYQVszndwP9/O6Yv8digrckYcH
RAkd1kw8jHK1t45Z4bUU63hMhHmHuKagjlarSoorQg2s9i65y+56oCryXQbn52cc
blwI3O5/6ziLPiuJ76TpvVmUk1S4qL+KkFcDN6GOBUylZtcMfFoaq2vnDKrLwgkC
h1PfYLRqtwgAtY5Y8XKCEAkcT0W+qcr0O2jLM7CdNkm46dtV00E47GskfHzLf9Pi
1QleOgkcb/Ki9S+UsxWHedFGDmlxgv8MzIfyy8lQmdV1lz6gyliYKBSbZfAltCGu
b/zixlcVsA06NbDTPsya
=LkP1
-----END PGP SIGNATURE-----
next reply other threads:[~2019-03-31 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 10:26 Michael Ellerman [this message]
2019-03-31 16:00 ` [GIT PULL] Please pull powerpc/linux.git powerpc-5.1-4 tag pr-tracker-bot
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=87pnq7l4qn.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@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;
as well as URLs for NNTP newsgroup(s).