From: Eric Blake <eblake@redhat.com>
To: Martin Kletzander <mkletzan@redhat.com>, qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>,
Anthony Liguori <aliguori@amazon.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] qmp: expose list of supported character device backends
Date: Fri, 31 Jan 2014 10:20:42 -0700 [thread overview]
Message-ID: <52EBDB6A.8000800@redhat.com> (raw)
In-Reply-To: <fd91a5bb6e9a10f9b5adf332bd66953bf4a75578.1391186851.git.mkletzan@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
On 01/31/2014 09:49 AM, Martin Kletzander wrote:
> Introduce 'query-chardev-backends' QMP command which lists all
> supported character device backends.
>
> Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
> ---
> v2:
> - Version changed from "1.8.0" to "2.0"
>
> qapi-schema.json | 22 ++++++++++++++++++++++
> qemu-char.c | 19 +++++++++++++++++++
> qmp-commands.hx | 41 +++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 82 insertions(+)
> +
> +-> { "execute": "query-chardev-backends" }
> +<- {
> + "return":[
> + {
> + "name":"udp",
> + },
Sorry for not noticing earlier, but this is not valid JSON. Lose the
trailing comma after each "name":"value", since the last element in a
JSON struct is not permitted to have a comma.
> + {
> + "name":"tcp",
> + },
> + {
> + "name":"unix",
> + },
> + {
> + "name":"spiceport",
> + }
With that change to all four spots,
Reviewed-by: Eric Blake <eblake@redhat.com>
--
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: 604 bytes --]
next prev parent reply other threads:[~2014-01-31 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 16:49 [Qemu-devel] [PATCH v2] qmp: expose list of supported character device backends Martin Kletzander
2014-01-31 17:20 ` Eric Blake [this message]
2014-02-01 11:44 ` Martin Kletzander
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=52EBDB6A.8000800@redhat.com \
--to=eblake@redhat.com \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mkletzan@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).