From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: "David Hildenbrand (Red Hat)" <david@kernel.org>,
Richard Henderson <richard.henderson@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Hendrik Brueckner <brueckner@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>
Subject: [PATCH v1] MAINTAINERS: s390 maintainer updates
Date: Thu, 20 Nov 2025 11:46:02 +0100 [thread overview]
Message-ID: <20251120104602.205718-1-david@kernel.org> (raw)
Unfortunately, I don't have a lot of capacity lately to take good care of
s390 in QEMU like I used to; and it doesn't look like that situation
will change. So let me convert myself to a reviewer in the s390 areas I
co-maintain.
Fortunately, we still have two other maintainers for "S390 floating
interrupt controller", so no action needed on that front.
For the other sections we get two new maintainers: Hendrik will
maintain "S390 CPU models" and Ilya will co-maintain "S390 TCG CPUs".
Thanks Hendrik and Ilya for stepping up!
Cc: Richard Henderson <richard.henderson@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: Halil Pasic <pasic@linux.ibm.com>
Cc: Hendrik Brueckner <brueckner@linux.ibm.com>
Cc: Matthew Rosato <mjrosato@linux.ibm.com>
Signed-off-by: David Hildenbrand (Red Hat) <david@kernel.org>
---
MAINTAINERS | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index d1c5080e50..d048c9f30d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -364,8 +364,8 @@ F: target/rx/
S390 TCG CPUs
M: Richard Henderson <richard.henderson@linaro.org>
-M: David Hildenbrand <david@kernel.org>
-R: Ilya Leoshkevich <iii@linux.ibm.com>
+M: Ilya Leoshkevich <iii@linux.ibm.com>
+R: David Hildenbrand <david@kernel.org>
S: Maintained
F: target/s390x/
F: target/s390x/tcg
@@ -1862,7 +1862,8 @@ F: target/s390x/ioinst.c
L: qemu-s390x@nongnu.org
S390 CPU models
-M: David Hildenbrand <david@kernel.org>
+M: Hendrik Brueckner <brueckner@linux.ibm.com>
+R: David Hildenbrand <david@kernel.org>
S: Maintained
F: target/s390x/cpu_features*.[ch]
F: target/s390x/cpu_models.[ch]
@@ -2919,7 +2920,7 @@ L: qemu-s390x@nongnu.org
S390 floating interrupt controller
M: Halil Pasic <pasic@linux.ibm.com>
M: Christian Borntraeger <borntraeger@linux.ibm.com>
-M: David Hildenbrand <david@kernel.org>
+R: David Hildenbrand <david@kernel.org>
R: Jason Herne <jjherne@linux.ibm.com>
S: Supported
F: hw/intc/s390_flic*.c
--
2.51.1
next reply other threads:[~2025-11-20 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 10:46 David Hildenbrand (Red Hat) [this message]
2025-11-20 10:53 ` [PATCH v1] MAINTAINERS: s390 maintainer updates Christian Borntraeger
2025-11-20 11:52 ` David Hildenbrand (Red Hat)
2025-11-20 11:33 ` Alex Bennée
2025-11-21 7:34 ` Thomas Huth
2025-11-21 8:17 ` David Hildenbrand (Red Hat)
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=20251120104602.205718-1-david@kernel.org \
--to=david@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=brueckner@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).