From: "Alex Bennée" <alex.bennee@linaro.org>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.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: Re: [PATCH v1] MAINTAINERS: s390 maintainer updates
Date: Thu, 20 Nov 2025 11:33:35 +0000 [thread overview]
Message-ID: <87jyzlhrao.fsf@draig.linaro.org> (raw)
In-Reply-To: <20251120104602.205718-1-david@kernel.org> (David Hildenbrand's message of "Thu, 20 Nov 2025 11:46:02 +0100")
"David Hildenbrand (Red Hat)" <david@kernel.org> writes:
> 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!
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-11-20 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 10:46 [PATCH v1] MAINTAINERS: s390 maintainer updates David Hildenbrand (Red Hat)
2025-11-20 10:53 ` Christian Borntraeger
2025-11-20 11:52 ` David Hildenbrand (Red Hat)
2025-11-20 11:33 ` Alex Bennée [this message]
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=87jyzlhrao.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=borntraeger@linux.ibm.com \
--cc=brueckner@linux.ibm.com \
--cc=david@kernel.org \
--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).