From: "Andreas Färber" <andreas.faerber@web.de>
To: Alexander Graf <agraf@suse.de>
Cc: mark.cave-ayland@ilande.co.uk, qemu-devel@nongnu.org,
chouteau@adacore.com, PReP <qemu-ppc@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Hervé Poussineau" <hpoussin@reactos.org>
Subject: Re: [Qemu-devel] [PATCH prep for-1.5] prep: Add ELF support for -bios
Date: Sun, 28 Apr 2013 12:30:55 +0200 [thread overview]
Message-ID: <517CFA5F.9040508@web.de> (raw)
In-Reply-To: <B2985FDB-1BF4-43CF-B386-1CCAA75ABAA8@suse.de>
Am 28.04.2013 12:22, schrieb Alexander Graf:
>
> On 28.04.2013, at 12:16, Andreas Färber wrote:
>
>> P.S. I am happy about your review comments, but you were not
>> intentionally CC'ed on a PReP patch - this is apparently the result of
>> Paolo having used hw/ppc/ pattern in the ppc TCG guest core section,
>> which used to be target-ppc/ only. Should we exclude prep.c and future
>> PReP files or even hw/ppc/ from that MAINTAINERS section? Similar
>
> I think having hw/ppc at least listed as CC to qemu-ppc@nongnu.org is a good idea. I'm not sure how much hassle it'll be to split maintainership inside of a directory. Does it mean we have to list all files individually? That'd be annoying :).
Well, what I was rather thinking of was removing F: hw/foo/ from all
"Guest CPU cores (TCG)" sections. We already have boards listed
individually under "PowerPC Machines", so this seems duplicate here;
alternatively it would certainly be possible to add a new heading for
hw/foo/ entries. I do not remember seeing any discussion about this
MAINTAINERS change nor us ack'ing it, so reverting would seem the most
natural solution.
Exclusion in the current scheme would mean adding:
X: hw/ppc/prep.c
Andreas
next prev parent reply other threads:[~2013-04-28 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 0:32 [Qemu-devel] [PATCH prep for-1.5] prep: Add ELF support for -bios Andreas Färber
2013-04-28 5:57 ` Hervé Poussineau
2013-04-28 9:44 ` Alexander Graf
2013-04-28 10:16 ` Andreas Färber
2013-04-28 10:22 ` Alexander Graf
2013-04-28 10:30 ` Andreas Färber [this message]
2013-04-29 10:14 ` Fabien Chouteau
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=517CFA5F.9040508@web.de \
--to=andreas.faerber@web.de \
--cc=agraf@suse.de \
--cc=chouteau@adacore.com \
--cc=hpoussin@reactos.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).