From: Amit Machhiwal <amachhiw@linux.ibm.com>
To: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Harsh Prateek Bora <harshpb@linux.ibm.com>
Cc: Amit Machhiwal <amachhiw@linux.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>,
Chinmay Rath <rathc@linux.ibm.com>,
Gautam Menghani <gautam@linux.ibm.com>
Subject: [PATCH] MAINTAINERS: Add myself as a reviewer for PPC KVM and sPAPR
Date: Wed, 19 Aug 2026 10:35:45 +0530 [thread overview]
Message-ID: <20260819050545.21232-1-amachhiw@linux.ibm.com> (raw)
I have been contributing to PPC KVM and sPAPR (pseries) for some time now and
would like to get notified of incoming changes to help with code reviews.
Signed-off-by: Amit Machhiwal <amachhiw@linux.ibm.com>
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b51f5c3e6022..1a1c77285d3d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -497,6 +497,7 @@ F: tests/functional/aarch64/test_kvm.py
PPC KVM CPUs
M: Nicholas Piggin <npiggin@gmail.com>
R: Harsh Prateek Bora <harshpb@linux.ibm.com>
+R: Amit Machhiwal <amachhiw@linux.ibm.com>
S: Odd Fixes
F: target/ppc/kvm.c
@@ -1661,6 +1662,7 @@ F: tests/functional/ppc/test_40p.py
sPAPR (pseries)
M: Nicholas Piggin <npiggin@gmail.com>
M: Harsh Prateek Bora <harshpb@linux.ibm.com>
+R: Amit Machhiwal <amachhiw@linux.ibm.com>
L: qemu-ppc@nongnu.org
S: Odd Fixes
F: hw/*/spapr*
base-commit: fa19879df1658f96ac07365fca8835b7decd6995
--
2.50.1 (Apple Git-155)
next reply other threads:[~2026-08-19 5:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 5:05 Amit Machhiwal [this message]
2026-08-19 7:12 ` [PATCH] MAINTAINERS: Add myself as a reviewer for PPC KVM and sPAPR Cédric Le Goater
2026-08-19 8:36 ` Amit Machhiwal
2026-08-19 7:19 ` Gautam Menghani
2026-08-19 10:00 ` Chinmay Rath
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=20260819050545.21232-1-amachhiw@linux.ibm.com \
--to=amachhiw@linux.ibm.com \
--cc=gautam@linux.ibm.com \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rathc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.