From: Eric Blake <eblake@redhat.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: mdroth@linux.vnet.ibm.com, kwolf@redhat.com, pbonzini@redhat.com,
armbru@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC 2/3] qapi script: add support of event
Date: Fri, 13 Dec 2013 06:31:03 -0700 [thread overview]
Message-ID: <52AB0C17.8020704@redhat.com> (raw)
In-Reply-To: <1384307094-5836-3-git-send-email-xiawenc@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
On 11/12/2013 06:44 PM, Wenchao Xia wrote:
> Nested structure is not supported now, so following define is not valid:
> { 'event': 'EVENT_C',
> 'data': { 'a': { 'a_a', 'str', 'a_b', 'str' }, 'b': 'int' }
But what IS valid? You need to document this in docs/qapi-code-gen.txt
at a bare minimum.
This patch series is hard to review, and still has the RFC subject line.
At this point, I think it's worth rebasing and resending what you have;
even if it needs more review, it will at least get it to a state that is
easier to review.
> +++ b/scripts/qapi-event.py
> @@ -0,0 +1,355 @@
> +#
> +# QAPI event generator
> +#
> +# Copyright IBM, Corp. 2013
> +#
> +# Authors:
> +# Wenchao Xia <xiawenc@linux.vnet.ibm.com>
> +#
> +# This work is licensed under the terms of the GNU GPLv2.
Can you please use GPLv2+ (that is, add the "or later" clause)? We
already have GPLv2-only code, but I don't want to increase the size of
that unfortunate license choice.
--
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-12-13 13:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 1:44 [Qemu-devel] [PATCH RFC 0/3] add direct support of event in qapi schema Wenchao Xia
2013-11-13 1:44 ` [Qemu-devel] [PATCH RFC 1/3] os-posix: include sys/time.h Wenchao Xia
2013-12-13 13:26 ` Eric Blake
2013-11-13 1:44 ` [Qemu-devel] [PATCH RFC 2/3] qapi script: add support of event Wenchao Xia
2013-11-28 0:48 ` Luiz Capitulino
2013-11-28 7:16 ` Wenchao Xia
2013-11-28 14:31 ` Luiz Capitulino
2013-12-02 6:48 ` Wenchao Xia
2013-12-13 3:00 ` Wenchao Xia
2013-12-13 13:31 ` Eric Blake [this message]
2013-12-13 13:43 ` Kevin Wolf
2013-12-16 2:50 ` Wenchao Xia
2013-12-16 9:04 ` Markus Armbruster
2013-12-16 9:13 ` Markus Armbruster
2014-01-07 12:14 ` Markus Armbruster
2014-01-13 10:08 ` Markus Armbruster
2014-01-15 1:47 ` Wenchao Xia
2014-01-16 2:50 ` Michael Roth
2014-01-16 11:05 ` Paolo Bonzini
2014-01-30 10:35 ` Markus Armbruster
2013-12-16 2:51 ` Wenchao Xia
2013-11-13 1:44 ` [Qemu-devel] [PATCH 2/2] try Wenchao Xia
2013-11-13 1:47 ` Wenchao Xia
2013-11-13 1:44 ` [Qemu-devel] [PATCH RFC 3/3] tests: add test cases for qapi event support Wenchao Xia
2013-12-13 13:36 ` Eric Blake
2013-12-16 2:55 ` Wenchao Xia
2013-12-16 3:12 ` Wenchao Xia
2014-01-02 2:30 ` Wenchao Xia
2013-11-22 2:03 ` [Qemu-devel] [PATCH RFC 0/3] add direct support of event in qapi schema Wenchao Xia
2013-11-22 14:33 ` Luiz Capitulino
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=52AB0C17.8020704@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiawenc@linux.vnet.ibm.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.