From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: christophe.leroy@c-s.fr, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-5.6-2 tag
Date: Sat, 08 Feb 2020 23:52:43 +1100 [thread overview]
Message-ID: <87ftfl1bs4.fsf@mpe.ellerman.id.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull two powerpc fixes for 5.6:
The following changes since commit 71c3a888cbcaf453aecf8d2f8fb003271d28073f:
Merge tag 'powerpc-5.6-1' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux (2020-02-04 13:06:46 +0000)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-5.6-2
for you to fetch changes up to d4bf905307a1c90a27714ff7a9fd29b0a2ceed98:
powerpc: Fix CONFIG_TRACE_IRQFLAGS with CONFIG_VMAP_STACK (2020-02-08 21:49:06 +1100)
- ------------------------------------------------------------------
powerpc fixes for 5.6 #2
Fix an existing bug in our user access handling, exposed by one of the bug fixes
we merged this cycle.
A fix for a boot hang on 32-bit with CONFIG_TRACE_IRQFLAGS and the recently
added CONFIG_VMAP_STACK.
Thanks to:
Christophe Leroy, Guenter Roeck.
- ------------------------------------------------------------------
Christophe Leroy (1):
powerpc: Fix CONFIG_TRACE_IRQFLAGS with CONFIG_VMAP_STACK
Michael Ellerman (1):
powerpc/futex: Fix incorrect user access blocking
arch/powerpc/include/asm/futex.h | 10 ++++++----
arch/powerpc/kernel/entry_32.S | 2 +-
2 files changed, 7 insertions(+), 5 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAl4+rucACgkQUevqPMjh
pYBy4Q/+OHH+G3jPH2sCPycqXNh3e0XbAymtAH7v01Lj6c1BSiWhvq1vP58mEeUM
TwssxNgQC7ZeltOHwZc/0GA7WPp4cYuHIU0XVuxKmj8LvWM3gqC0WUbaMkbz1uvz
mM5IN+WA9ENvzEX4A4y5vKzM/pEMVkyyXOluaUmFWCT+94bapYqlKUjeQqYySxwu
js4qBAuMULl4qr3zgMAa4WS3v3XgJ+Zj5v3Rh0O/ITpV/qv+/lQrBYlI6Q48/L5x
hYmQa+3ahCaVtxLnsDpZHrvfiv8UKpgZMjNYPgDfv0nPjTsngTXGB2RtLlD63a4t
Ve2uHLxoSvHGn2TTgUJ7N+VDuqGEYzHv0Ulg72SQBGz5kUKGeS8h0EdDI2naUNTS
OTicNI/DaGv9zCTChSXHEgrLc6mR+qLaamgqwjljF9iIxlKhr2cyD9/02d3XtrHH
2EKm8LCy+5pCtFjReUk+fENU9MZQ5+bYHtk/svcHCC63XXquHzwE+NdB6Whz/QPz
iV5NQW8EtU74u+wkPjdsmqta1IMmYzoisc4IULGEXgFJSjgYdYchkpKd0mf49QMG
Wmd4HQR5iMi2w2YiE25hyqa3nxWjHY2y3TV+b1JZZ4sAKOKCNLLZ6ey989SZKraw
xP9G/r7H7/TtMVA0aC1fcjVnxPzU4d+ygpVBtqL8u7T3/pul9dg=
=mWQt
-----END PGP SIGNATURE-----
next reply other threads:[~2020-02-08 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 12:52 Michael Ellerman [this message]
2020-02-08 22:35 ` [GIT PULL] Please pull powerpc/linux.git powerpc-5.6-2 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=87ftfl1bs4.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).