From: Shivang Upadhyay <shivangu@linux.ibm.com>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: hbathini@linux.ibm.com, sourabhjain@linux.ibm.com,
adityag@linux.ibm.com, harshpb@linux.ibm.com,
rathc@linux.ibm.com, npiggin@gmail.com, mahesh@linux.ibm.com,
Shivang Upadhyay <shivangu@linux.ibm.com>
Subject: [PATCH 0/3] hw/ppc: reorg PowerPC RAS code for better maintainability
Date: Tue, 14 Jul 2026 22:17:41 +0530 [thread overview]
Message-ID: <20260714164745.573141-1-shivangu@linux.ibm.com> (raw)
Extracting RAS related code from spapr_rtas.c, to a newly created spapr_rtas_ras.c
and carving out a MAINTAINERS entry dedicated to PowerPC RAS. This will cover RAS
related functionalities for PowerPC platforms.
Also adding myself as a reviewer, to help share the review workload.
Shivang Upadhyay (3):
hw/ppc: move RAS-specific RTAS handlers to spapr_rtas_ras.c
MAINTAINERS: add dedicated PowerPC RAS section
MAINTAINERS: add self as reviewer for PowerPC RAS
MAINTAINERS | 33 +++---
hw/ppc/meson.build | 1 +
hw/ppc/spapr_rtas.c | 189 --------------------------------
hw/ppc/spapr_rtas_ras.c | 232 ++++++++++++++++++++++++++++++++++++++++
4 files changed, 249 insertions(+), 206 deletions(-)
create mode 100644 hw/ppc/spapr_rtas_ras.c
--
2.54.0
next reply other threads:[~2026-07-14 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 16:47 Shivang Upadhyay [this message]
2026-07-14 16:47 ` [PATCH 1/3] hw/ppc: move RAS-specific RTAS handlers to spapr_rtas_ras.c Shivang Upadhyay
2026-07-16 4:44 ` Sourabh Jain
2026-07-14 16:47 ` [PATCH 2/3] MAINTAINERS: add dedicated PowerPC RAS section Shivang Upadhyay
2026-08-18 5:48 ` Aditya Gupta
2026-08-18 8:33 ` Sourabh Jain
2026-07-14 16:47 ` [PATCH 3/3] MAINTAINERS: add self as reviewer for PowerPC RAS Shivang Upadhyay
2026-08-18 5:49 ` Aditya Gupta
2026-07-15 14:39 ` [PATCH 0/3] hw/ppc: reorg PowerPC RAS code for better maintainability Vaibhav Jain
2026-07-15 14:52 ` Harsh Prateek Bora
2026-08-18 8:27 ` Sourabh Jain
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=20260714164745.573141-1-shivangu@linux.ibm.com \
--to=shivangu@linux.ibm.com \
--cc=adityag@linux.ibm.com \
--cc=harshpb@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=mahesh@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rathc@linux.ibm.com \
--cc=sourabhjain@linux.ibm.com \
/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