From: Max Reitz <mreitz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pkrempa@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.9] block: Declare blockdev-add and blockdev-del supported
Date: Wed, 22 Mar 2017 15:10:47 +0100 [thread overview]
Message-ID: <dbbe78d8-2c09-2832-89f4-51b50ee6bb8f@redhat.com> (raw)
In-Reply-To: <1490115473-24839-1-git-send-email-armbru@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1706 bytes --]
On 21.03.2017 17:57, Markus Armbruster wrote:
> It's been a long journey, but here we are.
>
> x-blockdev-remove-medium, x-blockdev-insert-medium and
> x-blockdev-change need a bit more work, so leave them alone for now.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> blockdev.c | 4 ++--
> qapi/block-core.json | 14 +++++---------
> tests/qemu-iotests/139 | 8 ++++----
> tests/qemu-iotests/141 | 4 ++--
> tests/qemu-iotests/147 | 2 +-
> 5 files changed, 14 insertions(+), 18 deletions(-)
[...]
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index 0f132fc..5d913d4 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -2907,11 +2907,7 @@
> # BlockBackend will be created; otherwise, @node-name is mandatory at the top
> # level and no BlockBackend will be created.
> #
> -# Note: This command is still a work in progress. It doesn't support all
> -# block drivers among other things. Stay away from it unless you want
> -# to help with its development.
> -#
> -# Since: 1.7
> +# Since: 2.9
> #
> # Example:
> #
> @@ -2957,7 +2953,7 @@
> { 'command': 'blockdev-add', 'data': 'BlockdevOptions', 'boxed': true }
>
> ##
> -# @x-blockdev-del:
> +# @blockdev-del:
> #
> # Deletes a block device that has been added using blockdev-add.
> # The command will fail if the node is attached to a device or is
> @@ -2969,7 +2965,7 @@
> # experimental. Stay away from it unless you want to help with its
> # development.
This part of the comment very much looks like it should be removed.
Max
> #
> -# Since: 2.5
> +# Since: 2.9
> #
> # Example:
> #
[...]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2017-03-22 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 16:57 [Qemu-devel] [PATCH for-2.9] block: Declare blockdev-add and blockdev-del supported Markus Armbruster
2017-03-21 17:08 ` Eric Blake
2017-03-22 6:07 ` Alexandre DERUMIER
2017-03-22 8:02 ` Markus Armbruster
2017-03-22 14:06 ` Markus Armbruster
2017-03-22 14:10 ` Max Reitz [this message]
2017-03-22 15:50 ` Markus Armbruster
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=dbbe78d8-2c09-2832-89f4-51b50ee6bb8f@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=pkrempa@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).