From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: aneesh.kumar@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-6.6-6 tag
Date: Fri, 27 Oct 2023 19:23:43 +1100 [thread overview]
Message-ID: <87edhgv5gw.fsf@mail.lhotse> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull some final powerpc fixes for 6.6:
The following changes since commit f9bc9bbe8afdf83412728f0b464979a72a3b9ec2:
powerpc/qspinlock: Fix stale propagated yield_cpu (2023-10-18 21:07:21 +1100)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.6-6
for you to fetch changes up to 47b8def9358c5eb888e78b24b7e5b7f2e2e97b8e:
powerpc/mm: Avoid calling arch_enter/leave_lazy_mmu() in set_ptes (2023-10-25 16:08:46 +1100)
- ------------------------------------------------------------------
powerpc fixes for 6.6 #6
- Fix boot crash with FLATMEM since set_ptes() introduction.
- Avoid calling arch_enter/leave_lazy_mmu() in set_ptes().
Thanks to: Aneesh Kumar K.V, Erhard Furtner.
- ------------------------------------------------------------------
Aneesh Kumar K.V (1):
powerpc/mm: Avoid calling arch_enter/leave_lazy_mmu() in set_ptes
Michael Ellerman (1):
powerpc/mm: Fix boot crash with FLATMEM
arch/powerpc/kernel/setup-common.c | 2 ++
arch/powerpc/mm/mem.c | 1 -
arch/powerpc/mm/pgtable.c | 32 ++++++++++++++------
3 files changed, 24 insertions(+), 11 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmU7ctsACgkQUevqPMjh
pYDD2xAAiDTlWc3AszHLgr/jj3hN++r/D6kso8sMbPPdqdLJ0Cumn41JdeOP3hO4
oEcr5L9ing1LG4KLDy94LCq/V5A7RmAIzOd0Dm6az35TL8J/LyLEFoncHaAG9O0F
mhGeuREsideLCwkeFosXONHPsf+yKpeVDi2yOCHO5wGkGAThgudvhhedVcSLBmco
2MbwuT0IOFhxDZjWUNZR/wslK9CGnOKVtHla7Kg3XX6NxCMKqRSFfO9lPXrBgPTP
EgV5B6aLHdb2JmC2vCNnYpHtkoXs4hotrzLXccFM1APtwbTKz2RYZpjmAtcupcj/
GDzG/n1hK72M1hFVRG9G09n+DLI0RZGOtNkp4F+078AbSMBdyzIMnudmX4b/N1kF
RLFYFri8N9HsYVar+x8jPcm3GV/GGAcFCuVJWKozoaEkojdpk+RZYAipjbQRKyeP
uW5/vfffFp2xNen7poMB/yxXosIW71YiHLtEq6LOOOKF9sioNK85qlJfMfYz6wXw
LRSJj4d3ZZJBZ8gXLN5EaGQ/uweUtqVpekaMW9c+J4cg+qhgoagYnzPoLp2KsDON
1Kr2aSTkX/YpR2d9jANSsO01m4hvoM0DAMTPVZS2EeIRGgNrxzLL9DkHalT4sGq1
tjSS3NV/uLd8OAYGkFqL3Ldcn6PX0tj5yWbYp9yzEAYx9yOgdOI=
=Rmou
-----END PGP SIGNATURE-----
reply other threads:[~2023-10-27 8:24 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=87edhgv5gw.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--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).