From: Luiz Capitulino <lcapitulino@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, wenchaoqemu@gmail.com
Subject: Re: [Qemu-devel] [PATCH for-2.1?] scripts: qapi-event.py: support vendor extension
Date: Wed, 9 Jul 2014 12:08:05 -0400 [thread overview]
Message-ID: <20140709120805.46a66a7e@redhat.com> (raw)
In-Reply-To: <53BD6339.2080305@redhat.com>
On Wed, 09 Jul 2014 09:43:53 -0600
Eric Blake <eblake@redhat.com> wrote:
> On 07/08/2014 12:17 PM, Luiz Capitulino wrote:
> > The event code generator barfs when it sees a dot in an event
> > argument, this makes it impossible to support vendor extensions
> > in event arguments as they always contain dots. Fix this by
> > replacing dots by hyphens in the generated code.
> >
> > PS: Event names and QMP command arguments may suffer from the
> > same issue, but I'm not checking/fixing them today.
> >
> > Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> > ---
> > scripts/qapi-event.py | 8 ++++----
> > scripts/qapi.py | 4 ++++
> > 2 files changed, 8 insertions(+), 4 deletions(-)
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
> This is borderline on whether it is a bug fix worth applying in 2.1 - it
> is fixing something that is new to this release (event-as-qapi) and
> which affects downstream vendors; but at the same time, it is something
> which cannot be triggered _except_ by downstream vendors, which are
> perfectly capable of applying this patch even if it misses 2.1. I'll
> leave it up to you.
I'm not sure it qualifies. On the one hand it's a bug in new code that
didn't exist before, on the other hand this is by far not blocker and
it doesn't cause any code to malfunction.
next prev parent reply other threads:[~2014-07-09 16:08 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 [this message]
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
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=20140709120805.46a66a7e@redhat.com \
--to=lcapitulino@redhat.com \
--cc=eblake@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 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).