From: Victor Toso <victortoso@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com
Subject: Re: [PATCH] Revert "qapi: fix examples of blockdev-add with qcow2"
Date: Tue, 4 Oct 2022 10:13:17 +0200 [thread overview]
Message-ID: <20221004081317.m7zewxcqbwabntkr@tapioca> (raw)
In-Reply-To: <20220930171908.846769-1-armbru@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3004 bytes --]
Hi,
Sorry taking some time to reply.
On Fri, Sep 30, 2022 at 07:19:08PM +0200, Markus Armbruster wrote:
> This reverts commit b6522938327141235b97ab38e40c6c4512587373.
Which is:
```
qapi: fix examples of blockdev-add with qcow2
The examples use "qcow2" driver with the wrong member name for
BlockdevRef alternate type. This patch changes all wrong member names
from "file" to "data-file" which is the correct member name in
BlockdevOptionsQcow2 for the BlockdevRef field.
Problem was noticed when using the example as a test case for Go
bindings.
```
> Kevin Wolf NAKed this patch, because:
>
> 'file' is a required member (defined in BlockdevOptionsGenericFormat),
> removing it makes the example invalid. 'data-file' is only an additional
> optional member to be used for external data files (i.e. when the guest
> data is kept separate from the metadata in the .qcow2 file).
You are correct. I apologize for the mistake. I trusted a bit too
much on the Go bindings and didn't realize that @file member was
actually present:
@BlockdevOptionsQcow2 >
@BlockdevOptionsGenericCOWFormat >
@BlockdevOptionsGenericCOWFormat >
@BlockdevOptionsGenericFormat
> However, it had already been merged then. Revert.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
Acked-by: Victor Toso <victortoso@redhat.com>
> ---
> qapi/block-core.json | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index f21fa235f2..882b266532 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -1541,8 +1541,8 @@
> # -> { "execute": "blockdev-add",
> # "arguments": { "driver": "qcow2",
> # "node-name": "node1534",
> -# "data-file": { "driver": "file",
> -# "filename": "hd1.qcow2" },
> +# "file": { "driver": "file",
> +# "filename": "hd1.qcow2" },
> # "backing": null } }
> #
> # <- { "return": {} }
> @@ -4378,7 +4378,7 @@
> # "arguments": {
> # "driver": "qcow2",
> # "node-name": "test1",
> -# "data-file": {
> +# "file": {
> # "driver": "file",
> # "filename": "test.qcow2"
> # }
> @@ -4395,7 +4395,7 @@
> # "cache": {
> # "direct": true
> # },
> -# "data-file": {
> +# "file": {
> # "driver": "file",
> # "filename": "/tmp/test.qcow2"
> # },
> @@ -4477,7 +4477,7 @@
> # "arguments": {
> # "driver": "qcow2",
> # "node-name": "node0",
> -# "data-file": {
> +# "file": {
> # "driver": "file",
> # "filename": "test.qcow2"
> # }
> --
> 2.37.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-10-04 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 17:19 [PATCH] Revert "qapi: fix examples of blockdev-add with qcow2" Markus Armbruster
2022-10-04 8:13 ` Victor Toso [this message]
2022-10-04 12:21 ` Victor Toso
2022-10-05 9:58 ` Kevin Wolf
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=20221004081317.m7zewxcqbwabntkr@tapioca \
--to=victortoso@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@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).