From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Christian Borntraeger <borntraeger@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>,
Thomas Huth <thuth@redhat.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 12:52:29 +0100 [thread overview]
Message-ID: <aea5c335-4f28-4f82-825a-229c4065eab0@kernel.org> (raw)
In-Reply-To: <cb7ac0cf-940a-4079-aa84-4433a4b49908@linux.ibm.com>
On 11/20/25 11:53, Christian Borntraeger wrote:
> Am 20.11.25 um 11:46 schrieb David Hildenbrand (Red Hat):
>> 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>
>
> Acked-by: Christian Borntraeger <borntraeger@linux.ibm.com>
>
> Thank you for your work on s390/kvm is the past. There would be no gdb,
> nesting, cpumodel and virtio-mem support without you for s390. You did
> an awesome job.
Thanks a lot for your kind word Christian, highly appreciated!
... without you, I wouldn't even have had the opportunity to do any of
that work and would likely not be doing the work I do today, so thanks
to you for that as well! :)
--
Cheers
David
next prev parent reply other threads:[~2025-11-20 11:52 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) [this message]
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=aea5c335-4f28-4f82-825a-229c4065eab0@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).