From: Kashyap Chamarthy <kchamart@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: qemu-devel@nongnu.org, libvir-list@redhat.com,
"Daniel P. Berrange" <berrange@redhat.com>,
David Gibson <dgibson@redhat.com>, Eric Blake <eblake@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [qemu RFC v3 1/3] qapi: add SysEmuTarget to "common.json"
Date: Tue, 24 Apr 2018 10:04:04 +0200 [thread overview]
Message-ID: <20180424080404.GO3502@paraplu> (raw)
In-Reply-To: <20180420231246.23130-2-lersek@redhat.com>
On Sat, Apr 21, 2018 at 01:12:44AM +0200, Laszlo Ersek wrote:
> We'll soon need an enumeration type that lists all the softmmu targets
> that QEMU (the project) supports. Introduce @SysEmuTarget to
> "common.json".
[...]
> Notes:
> RFCv3:
>
> - The patch is new in this version. [Dan, Markus]
>
> - The original idea was to call the new enum @Target; however, @Target
> generates exactly the TARGET_AARCH64, TARGET_ALPHA, TARGET_ARM, ...
> enumeration constants that conflict with the poisoned preprocessing
> macros of the same names. Hence @SysEmuTarget -- it's more accurate
> anyway, since we want it to stand for system emulation targets.
>
> - Also, we discussed defining the new type in either "common.json" or
> "misc.json". "misc.json" turned out to be a problem: "firmware.json"
> would then include "misc.json" for the new type's sake, but that
> inclusion would become the first appearance of "misc.json" -- within
> "firmware.json". That messed up the generated documentation. By adding
> the new type to "common.json", "misc.json" (see the 2nd patch) and
> "firmware.json" (see the 3rd patch) can both consume the new type
> without problems.
The last two points are interesting enough (for me) to still to keep in
the commit message, but that's minor :-)
> qapi/common.json | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
FWIW:
Reviewed-by: Kashyap Chamarthy <kchamart@redhat.com>
[...]
--
/kashyap
next prev parent reply other threads:[~2018-04-24 8:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 23:12 [Qemu-devel] [qemu RFC v3 0/3] qapi: add "firmware.json" Laszlo Ersek
2018-04-20 23:12 ` [Qemu-devel] [qemu RFC v3 1/3] qapi: add SysEmuTarget to "common.json" Laszlo Ersek
2018-04-23 9:52 ` Markus Armbruster
2018-04-23 18:45 ` Laszlo Ersek
2018-04-24 8:04 ` Kashyap Chamarthy [this message]
2018-04-20 23:12 ` [Qemu-devel] [qemu RFC v3 2/3] qapi: change the type of TargetInfo.arch from string to enum SysEmuTarget Laszlo Ersek
2018-04-23 9:50 ` Markus Armbruster
2018-04-23 18:42 ` Laszlo Ersek
2018-04-24 6:09 ` Markus Armbruster
2018-04-20 23:12 ` [Qemu-devel] [qemu RFC v3 3/3] qapi: add "firmware.json" Laszlo Ersek
2018-05-03 14:03 ` Laszlo Ersek
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=20180424080404.GO3502@paraplu \
--to=kchamart@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgibson@redhat.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).