From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
nixiaoming@huawei.com, ruscur@russell.cc
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-5.16-4 tag
Date: Sun, 19 Dec 2021 14:53:59 +1100 [thread overview]
Message-ID: <87lf0hl06g.fsf@mpe.ellerman.id.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull some more powerpc fixes for 5.16:
The following changes since commit 5bb60ea611db1e04814426ed4bd1c95d1487678e:
powerpc/32: Fix hardlockup on vmap stack overflow (2021-11-24 21:00:51 +1100)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-5.16-4
for you to fetch changes up to 8734b41b3efe0fc6082c1937b0e88556c396dc96:
powerpc/module_64: Fix livepatching for RO modules (2021-12-14 23:13:03 +1100)
- ------------------------------------------------------------------
powerpc fixes for 5.16 #4
Fix a recently introduced oops at boot on 85xx in some configurations.
Fix crashes when loading some livepatch modules with STRICT_MODULE_RWX.
Thanks to: Joe Lawrence, Russell Currey, Xiaoming Ni.
- ------------------------------------------------------------------
Russell Currey (1):
powerpc/module_64: Fix livepatching for RO modules
Xiaoming Ni (1):
powerpc/85xx: Fix oops when CONFIG_FSL_PMC=n
arch/powerpc/kernel/module_64.c | 42 ++++++++++++++++----
arch/powerpc/platforms/85xx/smp.c | 4 +-
2 files changed, 36 insertions(+), 10 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmG+rMQACgkQUevqPMjh
pYBLNQ/8DdqJFMgeVNV+RBinTdrtXl4RmMGvNE0ogmZ215GPiwjbjt2WYlMEg0Ol
4WrWSZwThKJdDXvR05HTU9QncNEXi1KIISfppNkNJQkRzRzs7HjDgFMjinNBsLzg
q3Q8LeGhj2eL3VNbavAr5UBsXgxJriGjrQQQj6NR2jyLZnITd+Wdn4/SWUgxdlmn
+aSKvoOWAUM3/+SrrhDmCsCKhM24bwoQ339uOp81j63oP6UVtr4dFVvDcVZyL+ea
tYSIQ5UeO8/zoaEMudZwFRifXmPk6+KiYzlzY+bx/6b5xXTv+B1oAT0RX+nvdv2g
aQIRI0EKsEf2OLD8ttlGKkF8NyXQBJjsDZ6VBklXTcSlIxMtSAJxz80USHk2FyHx
ojgi51Axdp031gA7bhq6jDvSO1izYR4S7si3Hqfzm4IxYMr5UnQSA5IJfsfMlASt
3qZBFpkN3rwFOERMa9IiLarnLzMiionvw7Vf2nESx+Uv/0sYS38528Z2xjBgagdd
OUA5h8XsC3NLUpbZtQy9R0+7jkDYXbe0r5BoPjmonkS90bR3/LhsO8eCWANqsaWO
2Jtu6V33PgAKZbR02V2o76t0WSzf3z72kOq7vsvcmc4tD6Lv4ph3d2ynjQ9oHizu
7FQqoFdHAA/Cbq/AiZqIVwE1pUpJIKesjr/JcNkagUsExLTnXQk=
=Xy0P
-----END PGP SIGNATURE-----
next reply other threads:[~2021-12-19 3:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 3:53 Michael Ellerman [this message]
2021-12-19 20:34 ` [GIT PULL] Please pull powerpc/linux.git powerpc-5.16-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=87lf0hl06g.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nixiaoming@huawei.com \
--cc=ruscur@russell.cc \
--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