From: Luiz Capitulino <lcapitulino@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: famz@redhat.com, Markus Armbruster <armbru@redhat.com>,
wenchaoqemu@gmail.com, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] scripts: qapi-event.py: support vendor extension
Date: Mon, 14 Jul 2014 14:32:44 -0400 [thread overview]
Message-ID: <20140714143244.6a2ba286@redhat.com> (raw)
In-Reply-To: <53C42204.6070909@redhat.com>
On Mon, 14 Jul 2014 12:31:32 -0600
Eric Blake <eblake@redhat.com> wrote:
> On 07/14/2014 12:12 PM, Luiz Capitulino wrote:
> >>>> Agree. Let's ditch nested structs and see whether there are any misuses
> >>>> of c_var() left.
> >>>
> >>> This is an honest question: do we really want to drop nested struct support,
> >>> wasn't it added by the block layer or am I just confused?
> >>
> >> We're talking about raw inline structs - there's only 3 impacted QAPI
> >> typesMP commands (if I counted correctly), and they have nothing to do
> >> with block layer complex structs. The idea is that we want to outlaw
> >> 'foo':{...} implicit structs, and instead require 'foo':'type', where
> >> 'type' was earlier defined with the {...} guts. The QMP wire format
> >> would be unchanged; it is just a change to the QAPI template that the
> >> generators read. Removing inline structs would also simplify the
> >> generators. Then, with that gone, we are free to to repurpose
> >> 'foo':{...} for default values of optional arguments. Here's a link to
> >> some of the earlier conversation:
> >>
> >> https://lists.gnu.org/archive/html/qemu-devel/2014-05/msg00708.html
> >> https://lists.gnu.org/archive/html/qemu-devel/2014-05/msg04268.html
> >
> > Right, this makes sense. Thanks for the URLs.
> >
> > Is there anyone planning on doing this? I don't think I'll have cycles
> > anytime soon... I'd be willing to merge my fix if nobody steps up.
>
> I may take a stab at removing raw inline structs after 2.1 is released,
> if no one beats me to it.
Great! Thanks a lot.
next prev parent reply other threads:[~2014-07-14 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 18:17 [Qemu-devel] [PATCH] scripts: qapi-event.py: support vendor extension Luiz Capitulino
2014-07-09 15:43 ` [Qemu-devel] [PATCH for-2.1?] " Eric Blake
2014-07-09 16:08 ` Luiz Capitulino
2014-07-10 14:31 ` [Qemu-devel] [PATCH] " Markus Armbruster
2014-07-10 14:36 ` Luiz Capitulino
2014-07-11 14:42 ` Markus Armbruster
2014-07-11 15:38 ` Eric Blake
2014-07-11 16:01 ` Markus Armbruster
2014-07-11 18:51 ` Luiz Capitulino
2014-07-11 21:22 ` Eric Blake
2014-07-14 18:12 ` Luiz Capitulino
2014-07-14 18:31 ` Eric Blake
2014-07-14 18:32 ` Luiz Capitulino [this message]
2014-07-10 16:13 ` Eric Blake
2014-07-23 14:19 ` Wenchao Xia
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=20140714143244.6a2ba286@redhat.com \
--to=lcapitulino@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wenchaoqemu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.