From: Fam Zheng <famz@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, pbonzini@redhat.com,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 7/7] QAPI: Fix blockdev-add example documentation
Date: Tue, 7 Feb 2017 18:29:09 +0800 [thread overview]
Message-ID: <20170207102909.GI19280@lemon.lan> (raw)
In-Reply-To: <56f34791aae2b2b5dff23ea927dfa42b54d452c6.1485365834.git.jcody@redhat.com>
On Wed, 01/25 12:42, Jeff Cody wrote:
> Signed-off-by: Jeff Cody <jcody@redhat.com>
> ---
> qapi/block-core.json | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index 4ebb8d8..adc089f 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -2909,21 +2909,24 @@
> # 1.
> # -> { "execute": "blockdev-add",
> # "arguments": {
> -# "options" : { "driver": "qcow2",
> -# "file": { "driver": "file",
> -# "filename": "test.qcow2" } } } }
> +# "driver": "qcow2",
> +# "node-name": "test1",
> +# "file": {
> +# "driver": "file",
> +# "filename": "test.qcow2"
> +# }
> +# }
> +# }
> # <- { "return": {} }
> #
> # 2.
> # -> { "execute": "blockdev-add",
> # "arguments": {
> -# "options": {
> # "driver": "qcow2",
> # "node-name": "node0",
> # "discard": "unmap",
> # "cache": {
> -# "direct": true,
> -# "writeback": true
> +# "direct": true
> # },
> # "file": {
> # "driver": "file",
> @@ -2936,7 +2939,6 @@
> # "filename": "/dev/fdset/4"
> # }
> # }
> -# }
> # }
> # }
> #
> @@ -2964,14 +2966,12 @@
> #
> # -> { "execute": "blockdev-add",
> # "arguments": {
> -# "options": {
> # "driver": "qcow2",
> # "node-name": "node0",
> # "file": {
> # "driver": "file",
> # "filename": "test.qcow2"
> # }
> -# }
> # }
> # }
> # <- { "return": {} }
> --
> 2.9.3
>
>
The alignments are a bit odd now but the syntax looks correct. Is it worth to
reindent while we are at it?
Fam
next prev parent reply other threads:[~2017-02-07 10:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 17:42 [Qemu-devel] [PATCH v2 0/7] iscsi: Add blockdev-add support Jeff Cody
2017-01-25 17:42 ` [Qemu-devel] [PATCH v2 1/7] iscsi: Split URL into individual options Jeff Cody
2017-02-07 10:06 ` Fam Zheng
2017-01-25 17:42 ` [Qemu-devel] [PATCH v2 2/7] iscsi: Handle -iscsi user/password in bdrv_parse_filename() Jeff Cody
2017-02-07 10:13 ` Fam Zheng
2017-02-17 13:26 ` Kevin Wolf
2017-02-17 14:09 ` Fam Zheng
2017-02-17 14:10 ` Fam Zheng
2017-01-25 17:42 ` [Qemu-devel] [PATCH v2 3/7] iscsi: Add initiator-name option Jeff Cody
2017-02-07 10:16 ` Fam Zheng
2017-01-25 17:42 ` [Qemu-devel] [PATCH v2 4/7] iscsi: Add header-digest option Jeff Cody
2017-02-07 10:18 ` Fam Zheng
2017-01-25 17:42 ` [Qemu-devel] [PATCH v2 5/7] iscsi: Add timeout option Jeff Cody
2017-02-07 10:21 ` Fam Zheng
2017-01-25 17:42 ` [Qemu-devel] [PATCH v2 6/7] iscsi: Add blockdev-add support Jeff Cody
2017-02-07 10:23 ` Fam Zheng
2017-02-17 21:40 ` Eric Blake
2017-02-17 21:47 ` Jeff Cody
2017-01-25 17:42 ` [Qemu-devel] [PATCH v2 7/7] QAPI: Fix blockdev-add example documentation Jeff Cody
2017-02-07 10:29 ` Fam Zheng [this message]
2017-01-25 17:57 ` [Qemu-devel] [PATCH v2 0/7] iscsi: Add blockdev-add support no-reply
2017-02-17 21:12 ` Jeff Cody
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=20170207102909.GI19280@lemon.lan \
--to=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.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 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).