From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 2/2] vmdk: Implment bdrv_get_specific_info
Date: Thu, 31 Oct 2013 10:12:21 -0600 [thread overview]
Message-ID: <52728165.3040206@redhat.com> (raw)
In-Reply-To: <1383185183-6552-3-git-send-email-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
On 10/30/2013 08:06 PM, Fam Zheng wrote:
> Implement .bdrv_get_specific_info to return the extent information.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
>
> ---
> v5: Changed 3 lines:
> - Save cid in vmdk_open. (Kevin)
> - Report parent_cid in vmdk_get_specific_info.
> - Rename create_type to create-type in qapi-schema.json.
>
> +++ b/qapi-schema.json
> @@ -225,6 +225,27 @@
> } }
>
> ##
> +# @ImageInfoSpecificVmdk:
> +#
> +# @create_type: The create type of VMDK image
Mismatch...
> +#
> +# @cid: Content id of image
> +#
> +# @parent-cid: Parent VMDK image's cid
> +#
> +# @extents: List of extent files
> +#
> +# Since: 1.7
> +##
> +{ 'type': 'ImageInfoSpecificVmdk',
> + 'data': {
> + 'create-type': 'str',
...from the actual spelling.
> + 'cid': 'int',
> + 'parent-cid': 'int',
> + 'extents': ['ImageInfo']
> + } }
> +
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
prev parent reply other threads:[~2013-10-31 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 2:06 [Qemu-devel] [PATCH v5 0/2] vmdk: Implement bdrv_get_specific_info Fam Zheng
2013-10-31 2:06 ` [Qemu-devel] [PATCH v5 1/2] qapi: Add optional field 'compressed' to ImageInfo Fam Zheng
2013-10-31 2:06 ` [Qemu-devel] [PATCH v5 2/2] vmdk: Implment bdrv_get_specific_info Fam Zheng
2013-10-31 16:12 ` Eric Blake [this message]
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=52728165.3040206@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).