From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qapi: Add (Since 1.8) to BlockInfo.dirty-bitmaps
Date: Thu, 14 Nov 2013 13:19:42 +0100 [thread overview]
Message-ID: <20131114121942.GD9755@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1384396401-4529-1-git-send-email-famz@redhat.com>
Am 14.11.2013 um 03:33 hat Fam Zheng geschrieben:
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> qapi-schema.json | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 931d710..3f2b5ef 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -949,7 +949,7 @@
> # (only present if removable is true)
> #
> # @dirty-bitmaps: #optional dirty bitmaps information (only present if the
> -# driver has one or more dirty bitmaps)
> +# driver has one or more dirty bitmaps) (Since 1.8)
> #
> # @io-status: #optional @BlockDeviceIoStatus. Only present if the device
> # supports it and the VM is configured to stop on errors
Thanks, updated the patch in my queue with this.
Kevin
next prev parent reply other threads:[~2013-11-14 12:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 10:29 [Qemu-devel] [PATCH v3 0/2] block: per caller dirty bitmap Fam Zheng
2013-11-13 10:29 ` [Qemu-devel] [PATCH v3 1/2] " Fam Zheng
2013-11-13 14:33 ` Fam Zheng
2013-11-13 14:36 ` Kevin Wolf
2013-11-13 10:29 ` [Qemu-devel] [PATCH v3 2/2] qapi: Change BlockDirtyInfo to list Fam Zheng
2013-11-13 14:19 ` Kevin Wolf
2013-11-13 14:40 ` Paolo Bonzini
2013-11-13 14:40 ` Fam Zheng
2013-11-14 2:13 ` Wenchao Xia
2013-11-14 2:22 ` Fam Zheng
2013-11-13 20:37 ` Eric Blake
2013-11-13 20:44 ` Eric Blake
2013-11-14 2:33 ` [Qemu-devel] [PATCH] qapi: Add (Since 1.8) to BlockInfo.dirty-bitmaps Fam Zheng
2013-11-14 12:19 ` Kevin Wolf [this message]
2013-11-14 1:31 ` [Qemu-devel] [PATCH v3 2/2] qapi: Change BlockDirtyInfo to list Wenchao Xia
2013-11-14 1:39 ` Fam Zheng
2013-11-14 2:03 ` Eric Blake
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=20131114121942.GD9755@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=famz@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 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).