From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Anthony Liguori" <aliguori@us.ibm.com>,
patches@linaro.org, qemu-trivial@nongnu.org,
"John Rigby" <john.rigby@linaro.org>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line
Date: Mon, 20 May 2013 10:41:19 -0600 [thread overview]
Message-ID: <519A522F.80305@redhat.com> (raw)
In-Reply-To: <1369066884-431-1-git-send-email-peter.maydell@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]
On 05/20/2013 10:21 AM, Peter Maydell wrote:
> Reformat the qapi-schema TargetType enumeration so that it has just
> one target architecture name per line. This allows patches for
> adding new targets to just add a single line, rather than having
> to reformat most of the list (resulting in a hard-to-check diff).
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> d15a9c23 is an example of what you get otherwise.
>
> I would much prefer it if we autogenerated this list so you didn't
> need to change this file at all to add a new target, but Anthony
> is against that; so this is at least an improvement.
Yep, that raises (once again) the question of dynamic introspection -
there's a difference between the maximum amount of information known at
compile time, and the subset of enum values that are actually usable at
runtime. This list is static (all known architectures), depending on
what solutions we come up with for dynamic introspection, maybe that
solution will also have a way for generating enum types.
>
> qapi-schema.json | 30 ++++++++++++++++++++++++++----
> 1 file changed, 26 insertions(+), 4 deletions(-)
At any rate, I see no harm in taking this patch as-is now, while we
still spend time thinking about introspection.
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-05-20 17:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 16:21 [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line Peter Maydell
2013-05-20 16:35 ` Paolo Bonzini
2013-05-20 16:38 ` Peter Maydell
2013-05-20 17:14 ` Paolo Bonzini
2013-05-22 13:15 ` Anthony Liguori
2013-05-22 13:50 ` Andreas Färber
2013-05-22 14:28 ` Anthony Liguori
2013-05-22 14:34 ` [Qemu-devel] New targets (was: [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line) Andreas Färber
2013-05-22 14:48 ` Anthony Liguori
2013-05-22 15:33 ` Peter Maydell
2013-05-22 16:10 ` Anthony Liguori
2013-05-22 13:51 ` [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line Peter Maydell
2013-05-22 14:29 ` Anthony Liguori
2013-05-22 14:38 ` Paolo Bonzini
2013-05-24 21:38 ` [Qemu-devel] [libvirt] " Eric Blake
2013-05-25 9:18 ` Peter Maydell
2013-05-25 12:31 ` Andreas Färber
2013-05-20 16:41 ` Eric Blake [this message]
2013-05-20 16:47 ` [Qemu-devel] " Peter Maydell
2013-05-20 16:57 ` Eric Blake
2013-05-20 17:05 ` Paolo Bonzini
2013-05-22 13:12 ` Anthony Liguori
2013-05-22 13:38 ` Peter Maydell
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=519A522F.80305@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=john.rigby@linaro.org \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).