From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ajd@linux.ibm.com, christophe.leroy@csgroup.eu,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
mpe@ellerman.id.au, namcao@linutronix.de, naveen@kernel.org,
npiggin@gmail.com, sourabhjain@linux.ibm.com
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-6.18-2 tag
Date: Sat, 18 Oct 2025 16:21:56 +0530 [thread overview]
Message-ID: <2de37987-076d-42c5-9597-0ef374f37e08@linux.ibm.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi Linus,
Please pull powerpc fixes for 6.18:
The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
tags/powerpc-6.18-2
for you to fetch changes up to 0843ba458439f38efdc14aa359c14ad0127edb01:
powerpc/fadump: skip parameter area allocation when fadump is
disabled (2025-10-13 09:41:31 +0530)
- ------------------------------------------------------------------
powerpc fixes for 6.18 #2
- Fix to handle NULL pointer dereference at irq domain teardown
- Fix for handling extraction of struct xive_irq_data
- Fix to skip parameter area allocation when fadump disabled
Thanks to: Ganesh Goudar, Hari Bathini, Nam Cao, Ritesh Harjani (IBM)
Sourabh Jain, Venkat Rao Bagalkote,
- ------------------------------------------------------------------
Nam Cao (2):
powerpc/pseries/msi: Fix NULL pointer dereference at irq domain
teardown
powerpc, ocxl: Fix extraction of struct xive_irq_data
Sourabh Jain (1):
powerpc/fadump: skip parameter area allocation when fadump is
disabled
arch/powerpc/kernel/fadump.c | 3 +++
arch/powerpc/kvm/book3s_xive.c | 12 ++++--------
arch/powerpc/platforms/powernv/vas.c | 2 +-
arch/powerpc/platforms/pseries/msi.c | 3 +--
arch/powerpc/sysdev/xive/common.c | 2 +-
drivers/misc/ocxl/afu_irq.c | 2 +-
6 files changed, 11 insertions(+), 13 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEqX2DNAOgU8sBX3pRpnEsdPSHZJQFAmjzb88ACgkQpnEsdPSH
ZJQVzQ//dleWxaoTyBWXOmES675XjSF2jy4vHCF73+xlp7zGuQ0XTyKPvqzQxUvT
ZG5fbVDeZA12sMU+6gtEa9WKAvI0xjk2OYoFs3Q1baoKyCYYL1v5NOzH7P/B2rw0
0jopt+LnCPzSGxJbcrCzrfvo3e8U2gTBXlssYa/hdNb3QiaF08Gxg66Yj+PNwmZC
dPumXXEvMO+wf0o9NFAMwlPRWLtLTtwET7jT64l0i2VMeClnq9sq3QpCzfBxHCGA
9jrDuEI8m2bJ175zLzZd9gNFlM9OGfAUTFhPMr7D6HIUsBAj9cyoF8yAe0CM2hIF
2ZfAkr+/8akobXB5IPL8sjth1sxUhDAVYrUfQ+L1MDFgqEdnNfDiP25jDdz4L3o3
zboUiHTXb2thVgTQTJNKHgkGQvKbj/mv+6ewJdpsut3UCXU91yCiE/cntCSRb0tw
fysnMZ3HLpe8c9PnhbyW5VMnBMo/rRzzaPRXxOnJ9wWJ0nsLOBvxjxbHnSmZ/6Hz
P7BepcEBFckBcLRdzeDWT3/Y1j2ZJhQl03F6exhZv8ePwS9o0uo3ThfBjxrGPh2v
8IDq1fvgIR+uWgXkl4Ap4kKfuk7xjlrqHFcYmXlx08WfjYrz9oejDGWM9qQn0/oO
6XOTrAxaBlyYJsE2IPE1sLQoQuC3BuN/coBeoTGuihmsPXw2+NM=
=pqn/
-----END PGP SIGNATURE-----
next reply other threads:[~2025-10-18 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 10:51 Madhavan Srinivasan [this message]
2025-10-18 17:27 ` [GIT PULL] Please pull powerpc/linux.git powerpc-6.18-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=2de37987-076d-42c5-9597-0ef374f37e08@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=ajd@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=namcao@linutronix.de \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=sourabhjain@linux.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).