From: Thomas Huth <thuth@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: "Eric Farman" <farman@linux.ibm.com>,
"David Hildenbrand" <david@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Halil Pasic" <pasic@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH RFC v2] MAINTAINERS: split out s390x sections
Date: Tue, 18 Jan 2022 10:16:03 +0100 [thread overview]
Message-ID: <23027d70-f144-61e9-1a74-e3511e5509ab@redhat.com> (raw)
In-Reply-To: <20211222105548.356852-1-cohuck@redhat.com>
On 22/12/2021 11.55, Cornelia Huck wrote:
> Split out some more specialized devices etc., so that we can build
> smarter lists of people to be put on cc: in the future.
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> Acked-by: David Hildenbrand <david@redhat.com>
> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Acked-by: Thomas Huth <thuth@redhat.com>
> Acked-by: Halil Pasic <pasic@linux.ibm.com>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
>
> v1->v2: move some sections to "Devices", some minor tweaks
>
> I guess that can go with the next set of s390x patches.
Indeed. Queued to my s390x-next branch now (together with Eric's update):
https://gitlab.com/thuth/qemu/-/commits/s390x-next/
Thomas
prev parent reply other threads:[~2022-01-18 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 10:55 [PATCH RFC v2] MAINTAINERS: split out s390x sections Cornelia Huck
2022-01-05 18:27 ` Eric Farman
2022-01-12 10:23 ` Cornelia Huck
2022-01-12 14:40 ` Eric Farman
2022-01-12 16:40 ` [RFC PATCH] MAINTAINERS: Add myself to s390 I/O areas Eric Farman
2022-01-12 22:13 ` Halil Pasic
2022-01-14 6:44 ` Christian Borntraeger
2022-01-18 9:16 ` Thomas Huth [this message]
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=23027d70-f144-61e9-1a74-e3511e5509ab@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
/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).