From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH 06/12] qapi: add socket address types
Date: Wed, 19 Sep 2012 11:20:28 -0600 [thread overview]
Message-ID: <5059FEDC.6020900@redhat.com> (raw)
In-Reply-To: <1348065078-5139-7-git-send-email-pbonzini@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
On 09/19/2012 08:31 AM, Paolo Bonzini wrote:
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> qapi-schema.json | 53 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file modificato, 53 inserzioni(+)
>
> ##
> +# @IPSocketAddress
> +#
> +# Captures the destination address of an IP socket
Given the presence of @to, would this read better as:
IP socket or socket range
> +#
> +# @host: host part of the address
> +#
> +# @port: port part of the address, or lowest port if @to is present
> +#
> +# @to: highest port to try
> +#
> +# @ipv4: whether to accept IPv4 addresses, default try both IPv4 and IPv6
> +# #optional
Isn't the #optional supposed to occur first after the colon, as in:
@ipv4: #optional whether to accept IPv4...
> +#
> +# @ipv6: whether to accept IPv6 addresses, default try both IPv4 and IPv6
> +# #optional
> +#
> +# Since 1.3
> +##
> +{ 'type': 'IPSocketAddress',
> + 'data': {
> + 'host': 'str',
> + 'port': 'str',
> + '*to': 'uint16',
Why is 'port' a string, but 'to' a uint16? Shouldn't they both be uint16?
--
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: 617 bytes --]
next prev parent reply other threads:[~2012-09-19 17:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 14:31 [Qemu-devel] [PATCH 00/12] QAPI prerequisites for the embedded NBD server Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 01/12] monitor: use monitor_handle_fd_param for non-Error-friendly users of named fds Paolo Bonzini
2012-09-19 20:42 ` Luiz Capitulino
2012-09-20 8:09 ` Paolo Bonzini
2012-09-20 13:47 ` Luiz Capitulino
2012-09-20 14:33 ` Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 02/12] monitor: add Error * argument to monitor_get_fd Paolo Bonzini
2012-09-19 20:47 ` Luiz Capitulino
2012-09-19 14:31 ` [Qemu-devel] [PATCH 03/12] qapi: do not protect enum values from namespace pollution Paolo Bonzini
2012-09-20 14:07 ` Luiz Capitulino
2012-09-19 14:31 ` [Qemu-devel] [PATCH 04/12] qapi: add "unix" to the set of reserved words Paolo Bonzini
2012-09-19 15:46 ` Peter Maydell
2012-09-19 15:58 ` Paolo Bonzini
2012-09-19 16:02 ` Paolo Bonzini
2012-09-19 19:29 ` Blue Swirl
2012-09-20 14:08 ` Luiz Capitulino
2012-09-19 14:31 ` [Qemu-devel] [PATCH 05/12] build: add QAPI files to the tools Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 06/12] qapi: add socket address types Paolo Bonzini
2012-09-19 17:20 ` Eric Blake [this message]
2012-09-20 8:01 ` Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 07/12] qemu-sockets: add error propagation to inet_parse Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 08/12] qemu-sockets: add error propagation to Unix socket functions Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 09/12] qemu-sockets: return IPSocketAddress from inet_parse Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 10/12] qemu-sockets: move block from QemuOpts to arguments Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 11/12] qemu-sockets: add block and in_progress arguments to unix_connect_opts Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 12/12] qemu-sockets: add socket_listen, socket_connect, socket_parse Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 13/12] block: add close notifiers Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 14/12] qmp: add NBD server commands Paolo Bonzini
2012-09-19 17:48 ` Eric Blake
2012-09-20 8:01 ` Paolo Bonzini
2012-09-19 14:31 ` [Qemu-devel] [PATCH 15/12] hmp: " Paolo Bonzini
2012-09-19 18:02 ` Eric Blake
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=5059FEDC.6020900@redhat.com \
--to=eblake@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@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).