From: Eric Blake <eblake@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v2 1/2] net: Drop the legacy "name" parameter from the -net option
Date: Tue, 12 May 2020 09:26:53 -0500 [thread overview]
Message-ID: <34b66d39-27ce-36a9-b478-c17cbd1e5712@redhat.com> (raw)
In-Reply-To: <20200512123149.30207-2-thuth@redhat.com>
On 5/12/20 7:31 AM, Thomas Huth wrote:
> It's been deprecated since QEMU v3.1, so it's time to finally
> remove it. The "id" parameter can simply be used instead.
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> docs/system/deprecated.rst | 15 +++++++++------
> net/net.c | 10 +---------
> qapi/net.json | 3 ---
> 3 files changed, 10 insertions(+), 18 deletions(-)
>
> +++ b/qapi/net.json
> @@ -474,8 +474,6 @@
> #
> # @id: identifier for monitor commands
> #
> -# @name: identifier for monitor commands, ignored if @id is present
> -#
> # @opts: device type specific properties (legacy)
> #
> # Since: 1.2
> @@ -483,7 +481,6 @@
> { 'struct': 'NetLegacy',
> 'data': {
> '*id': 'str',
> - '*name': 'str',
> 'opts': 'NetLegacyOptions' } }
Why is 'id' left optional? I'd expect it to be mandatory, now.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-05-12 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 12:31 [PATCH v2 0/2] net: Drop legacy "name" from -net and remove NetLegacy Thomas Huth
2020-05-12 12:31 ` [PATCH v2 1/2] net: Drop the legacy "name" parameter from the -net option Thomas Huth
2020-05-12 14:26 ` Eric Blake [this message]
2020-05-12 14:50 ` Thomas Huth
2020-05-12 12:31 ` [PATCH v2 2/2] net: Drop the NetLegacy structure, always use Netdev instead Thomas Huth
2020-05-12 14:32 ` Eric Blake
2020-05-12 15:13 ` Thomas Huth
2020-05-12 15:51 ` Eric Blake
2020-05-13 8:40 ` Thomas Huth
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=34b66d39-27ce-36a9-b478-c17cbd1e5712@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 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).