All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, Greg Kurz <groug@kaod.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qemu v2] tap: Allow specifying a bridge
Date: Wed, 14 Sep 2016 08:54:16 -0500	[thread overview]
Message-ID: <05a37cbe-6ddf-482f-3cc1-ab98ef857a36@redhat.com> (raw)
In-Reply-To: <029cd2cc-56e4-9299-3f77-8a0de0a9d35f@ozlabs.ru>

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

On 09/13/2016 11:23 PM, Alexey Kardashevskiy wrote:

>>>
>>> Also, we don't have to abbreviate; 'bridge-name' may be easier to
>>> understand than 'br', as well as a mention of the default value if the
>>> parameter is not supplied.
> 
> 
> The existing NetdevBridgeOptions does not do this in json as well and it
> does in qemu-options.hx, so does my patch. Do I have to fix a bridge first
> before reposting this patch?...

If that interface is already baked in as 'br', then leave it alone.

> 
> When exactly is the content of qapi-schema.json's comments shown to a user?

Not yet, but Marc-Andre has patches pending that merge qemu-options.hx
and qemu-schema.json so that we have a single file with documentation,
rather than two semi-inconsistent copies.

> 
> 
>>>
>>
>> FWIW @br is consistent with what we already have in NetdevBridgeOptions
>> since 1.2.
> 
> Right, this is why "br=".

Okay, the argument of consistency with pre-existing interfaces is
reasonable.

-- 
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:[~2016-09-14 13:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13  7:11 [Qemu-devel] [PATCH qemu v2] tap: Allow specifying a bridge Alexey Kardashevskiy
2016-09-13 14:49 ` Eric Blake
2016-09-13 15:39   ` Greg Kurz
2016-09-14  4:23     ` Alexey Kardashevskiy
2016-09-14 13:54       ` Eric Blake [this message]
2016-09-14 14:17 ` Greg Kurz
2016-09-14 15:12   ` Eric Blake
2016-09-22  7:03     ` Jason Wang
2016-09-14 21:04 ` Paolo Bonzini
2016-09-19  0:33   ` Alexey Kardashevskiy
2016-09-19 11:59     ` Paolo Bonzini
2016-09-22  7:05       ` Jason Wang

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=05a37cbe-6ddf-482f-3cc1-ab98ef857a36@redhat.com \
    --to=eblake@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=groug@kaod.org \
    --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.