From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Michael S. Tsirkin" <mst@redhat.com>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Yongbok Kim" <yongbok.kim@mips.com>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Thomas Huth" <thuth@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] isa/piix: move to mips
Date: Fri, 5 Jan 2018 16:15:18 -0300 [thread overview]
Message-ID: <CAAdtpL4WQhtLOZcRSTFvTbLGs7f4miRKTPtE-uqrP0h2qOm32A@mail.gmail.com> (raw)
In-Reply-To: <1515108094-11508-1-git-send-email-mst@redhat.com>
Hi Michael,
On Thu, Jan 4, 2018 at 8:21 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> This device is only used on mips, move to the correct maintainer
> section.
>
> Cc: Aurelien Jarno <aurelien@aurel32.net>
> Cc: Yongbok Kim <yongbok.kim@mips.com>
> Cc: Hervé Poussineau <hpoussin@reactos.org>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 0255113..ab30f1f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -175,6 +175,7 @@ F: include/hw/intc/mips_gic.h
> F: include/hw/timer/mips_gictimer.h
> F: tests/tcg/mips/
> F: disas/mips.c
> +F: hw/isa/piix4.c
NACK this isn't the correct section (MIPS architecture),
The section you want to update is the "Malta board" one.
Now the 82371 devices are broadly use with X86 machines, so I am a bit
reluctant to this change.
Maybe I am misunderstanding the 'X86 machines PC' entry, but I see you
are the unique maintainer of this entry which status is "Supported:
Someone is actually paid to look after this".
My guess is you are paid to work on _recent_ PC machines and you are
probably receiving too many patches.
I suggest we split this section in "recent PC" vs "outdated PC".
It might be hard to draw a line, but maybe i440FX vs Q35 is a good one.
If you agree to unburden some files you don't find relevant to the
"recent PC" entry,
Hervé and I volunteer for the "outdated PC" one with a "Odd Fixes" status
(has a maintainer but they don't have time to do much other than throw
the odd patch in).
I hope you won't take this suggestion badly, we just offer help :)
Regards,
Phil.
> Moxie
> M: Anthony Green <green@moxielogic.com>
> @@ -849,7 +850,6 @@ F: hw/pci-host/q35.c
> F: hw/pci-host/pam.c
> F: include/hw/pci-host/q35.h
> F: include/hw/pci-host/pam.h
> -F: hw/isa/piix4.c
> F: hw/isa/lpc_ich9.c
> F: hw/i2c/smbus_ich9.c
> F: hw/acpi/piix4.c
> --
> MST
next prev parent reply other threads:[~2018-01-05 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 23:21 [Qemu-devel] [PATCH] isa/piix: move to mips Michael S. Tsirkin
2018-01-05 11:44 ` Paolo Bonzini
2018-01-05 19:15 ` Philippe Mathieu-Daudé [this message]
2018-01-08 16:41 ` Michael S. Tsirkin
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=CAAdtpL4WQhtLOZcRSTFvTbLGs7f4miRKTPtE-uqrP0h2qOm32A@mail.gmail.com \
--to=f4bug@amsat.org \
--cc=aurelien@aurel32.net \
--cc=hpoussin@reactos.org \
--cc=marcandre.lureau@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=yongbok.kim@mips.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).