From: Paolo Bonzini <pbonzini@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: armbru@redhat.com, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qmp-commands: fix incorrect uses of ":O" specifier
Date: Wed, 15 Apr 2015 14:21:25 +0200 [thread overview]
Message-ID: <552E57C5.1000407@redhat.com> (raw)
In-Reply-To: <w51oamp1t5w.fsf@maestria.local.igalia.com>
On 15/04/2015 14:18, Alberto Garcia wrote:
> On Wed 15 Apr 2015 01:30:04 PM CEST, Paolo Bonzini wrote:
>
>> As far as the QMP parser is concerned, neither the 'O' nor the 'q'
>> format specifiers put any constraint on the command. However, there
>> are two differences:
>>
>> 1) from a documentation point of view 'O' says that this command takes
>> a dictionary. The dictionary will be converted to QemuOpts in the
>> handler to match the corresponding HMP command.
>
> Is that documentation the comments in monitor.c? It could also be a good
> moment to document there 'q' as well.
No, I mean what you can learn by parsing the .args_type line.
'foo:O' means there will typically be no argument named foo, and the
dictionary will be treated as a series of key/value pairs.
'foo:q' means there will be an argument named foo, which is a JSON
object of some kind.
Paolo
> Otherwise the patch looks good to me,
>
> Reviewed-by: Alberto Garcia <berto@igalia.com>
>
> Berto
>
next prev parent reply other threads:[~2015-04-15 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 11:30 [Qemu-devel] [PATCH] qmp-commands: fix incorrect uses of ":O" specifier Paolo Bonzini
2015-04-15 12:18 ` Alberto Garcia
2015-04-15 12:21 ` Paolo Bonzini [this message]
2015-04-21 14:09 ` 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=552E57C5.1000407@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@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).