From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
npiggin@gmail.com
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-6.6-5 tag
Date: Sun, 22 Oct 2023 12:39:26 +1100 [thread overview]
Message-ID: <87y1fv4er5.fsf@mail.lhotse> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull some more powerpc fixes for 6.6:
The following changes since commit f0eee815babed70a749d2496a7678be5b45b4c14:
powerpc/47x: Fix 47x syscall return crash (2023-10-11 09:31:26 +1100)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.6-5
for you to fetch changes up to f9bc9bbe8afdf83412728f0b464979a72a3b9ec2:
powerpc/qspinlock: Fix stale propagated yield_cpu (2023-10-18 21:07:21 +1100)
- ------------------------------------------------------------------
powerpc fixes for 6.6 #5
- Fix stale propagated yield_cpu in qspinlocks leading to lockups.
- Fix broken hugepages on some configs due to ARCH_FORCE_MAX_ORDER.
- Fix a spurious warning when copros are in use at exit time.
Thanks to: Nicholas Piggin, Christophe Leroy, Nysal Jan K.A Sachin Sant,
Shrikanth Hegde.
- ------------------------------------------------------------------
Michael Ellerman (2):
powerpc/mm: Allow ARCH_FORCE_MAX_ORDER up to 12
powerpc/64s/radix: Don't warn on copros in radix__tlb_flush()
Nicholas Piggin (1):
powerpc/qspinlock: Fix stale propagated yield_cpu
arch/powerpc/Kconfig | 2 +-
arch/powerpc/lib/qspinlock.c | 3 +++
arch/powerpc/mm/book3s64/radix_tlb.c | 9 +--------
3 files changed, 5 insertions(+), 9 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmU0fBgACgkQUevqPMjh
pYCoUQ/+Jg66lC4D2tIcGFX7gHmWkHgx5uqchuTNB4GtI4W55eJaN/ZMdhUiJ5Gg
DsTjWlXnRY+sYBgXJw/ptZHoclYyN3SAEn/M+Zq1XYJNTjpg6TjNZpuuIzCgUYUd
AnNz54v8fCoHH7Yfc4T774gUq3c9WKQlQLF9dwkD67lQDfwwaMERLKpuXz/NKfrQ
+kvRplC0PkW0N0GY9w8PlYbd04MtjpOHucfQtaRAV2m/hRl0TPoHtteTwzcwieJC
pUuycjCIjy/PRJtUHOuHCFUq7hPshOAEg0R/cJ4/uJfOAjAlR7aPFhj9S6EhmALN
IURp3KgeUqri1e5ZSJ+ue5y3+/9fO/WD9FAeOgZJwY2HS4rEqIPgMc/H8oPKINUQ
BUmjfYmpYgMsnOK3/70Yt8CVmDDn6bmAs3cdDa12udYP+TZevdxskIAOUgW/bRWe
xHvf+JRAtCiqAKFsHhuO/sib1TtQGBNVJKydrJ+S8cUJf0IF5f0R+ns+piG1lc7+
05qvANSNpKgnvVSrXnS5Op9CfR6a6l9h1CJzJlCSJMp9a7yZ/6rDQQ8jt1sxVSdG
23xwUbQguveb6nf+UZQ2RPfdpTZTaxD2rHN6uAyCOqrNpu/ac4HaeGGCqHJdq8g2
S0sk1fi5bUKbcBepJuT4HMJTPLpJLnYlvjlzCKS/oEUc9d+cDf8=
=xp3d
-----END PGP SIGNATURE-----
next reply other threads:[~2023-10-22 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 1:39 Michael Ellerman [this message]
2023-10-22 1:52 ` [GIT PULL] Please pull powerpc/linux.git powerpc-6.6-5 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=87y1fv4er5.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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