All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Knut Omang <knuto@ifi.uio.no>
Subject: Re: [Qemu-devel] [PATCH] qapi-schema: mark InetSocketAddress as mandatory again
Date: Thu, 22 Oct 2015 07:57:04 -0600	[thread overview]
Message-ID: <5628EB30.2040400@redhat.com> (raw)
In-Reply-To: <20151022124215.GF9079@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

On 10/22/2015 06:42 AM, Daniel P. Berrange wrote:

>>> +++ b/qapi-schema.json
>>> @@ -2614,9 +2614,7 @@
>>>  #
>>>  # @host: host part of the address
>>>  #
>>> -# @port: port part of the address, or lowest port if @to is present.
>>> -#        Kernel selects a free port if omitted for listener addresses.
>>> -#        #optional
>>> +# @port: port part of the address, or lowest port if @to is present
>>
>> Don't you still want to allow an empty string as the way to allow kernel
>> port selection?
> 
> I only needed the support for empty port for the sake of the unit
> tests, which doesn't use QAPI parsing code. Enabling it via the command
> line / monitor was just a happy accident, so I figure this is fine for
> 2.5. We can re-revert it in 2.6 when you change the QAPI generator

Fair enough; then you can add:
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 --]

  reply	other threads:[~2015-10-22 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 10:25 [Qemu-devel] [PATCH] qapi-schema: mark InetSocketAddress as mandatory again Daniel P. Berrange
2015-10-22 12:22 ` Eric Blake
2015-10-22 12:42   ` Daniel P. Berrange
2015-10-22 13:57     ` Eric Blake [this message]
2015-10-29  6:32 ` Markus Armbruster

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=5628EB30.2040400@redhat.com \
    --to=eblake@redhat.com \
    --cc=berrange@redhat.com \
    --cc=knuto@ifi.uio.no \
    --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 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.