From: Fam Zheng <famz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Luiz Capitulino" <lcapitulino@redhat.com>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Benoît Canet" <benoit.canet@nodalink.com>
Subject: Re: [Qemu-devel] BB name vs. BDS name in the QAPI schema
Date: Mon, 15 Sep 2014 09:31:58 +0800 [thread overview]
Message-ID: <20140915013158.GA2639@fam-t430.nay.redhat.com> (raw)
In-Reply-To: <8738bvv4dm.fsf@blackfin.pond.sub.org>
On Sat, 09/13 19:04, Markus Armbruster wrote:
>
> I actually like having separate parameters for separate kinds of names.
>
> However, BlockdevRef appears to tie our hand: it's an anonymous union,
> which means only the value is on the wire, and the receiving end uses
> its type to determine which union member it is. Both kinds of names are
> strings, so we can't have separate union members for them.
>
> Opinions?
Why wouldn't it work without distinguishing it in the QAPI side?
I remember at the time of introducing node-name, it was in a separate
namespace, but now it's not. Then why should the user care *whether* a name is
"device" or "node-name"?
Fam
next prev parent reply other threads:[~2014-09-15 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 17:04 [Qemu-devel] BB name vs. BDS name in the QAPI schema Markus Armbruster
2014-09-15 1:31 ` Fam Zheng [this message]
2014-09-15 8:59 ` Kevin Wolf
2014-09-15 9:15 ` Fam Zheng
2014-09-15 15:01 ` Stefan Hajnoczi
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=20140915013158.GA2639@fam-t430.nay.redhat.com \
--to=famz@redhat.com \
--cc=armbru@redhat.com \
--cc=benoit.canet@nodalink.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.