From: Max Reitz <mreitz@redhat.com>
To: famz@redhat.com, Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/2] vmdk: implment bdrv_get_specific_info
Date: Fri, 11 Oct 2013 14:27:58 +0200 [thread overview]
Message-ID: <5257EECE.6060809@redhat.com> (raw)
In-Reply-To: <20131011120733.GB17449@T430s.nay.redhat.com>
On 2013-10-11 14:07, Fam Zheng wrote:
> On Fri, 10/11 05:52, Eric Blake wrote:
>> On 10/11/2013 02:31 AM, Fam Zheng wrote:
>>> Implement .bdrv_get_specific_info to return the extent information.
>>>
>>> Signed-off-by: Fam Zheng <famz@redhat.com>
>>> ---
>>> +
>>> + *spec_info->vmdk = (ImageInfoSpecificVmdk) {
>>> + .create_type = g_strdup(s->create_type),
>>> + .cid = s->cid,
>>> + };
>>> +
>>>
>>> ##
>>> +# @ImageInfoSpecificVmdk:
>>> +#
>>> +# @create_type: The create type of VMDK image
>> Is it worth making this an enum type rather than an open-coded string?
>> But that's not a show-stopper to me.
> For now I think a string is good enough, it's only used to display with
> qemu-img info, string type saves converting in opening code, as well as
> repeating type names in multiple places.
Actually, it can be queried through QMP (query-block) as well. But I
personally don't oppose using a string here.
Max
next prev parent reply other threads:[~2013-10-11 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 8:31 [Qemu-devel] [PATCH v2 0/2] vmdk: Implement bdrv_get_specific_info Fam Zheng
2013-10-11 8:31 ` [Qemu-devel] [PATCH v2 1/2] qapi: Add optional field 'compressed' to ImageInfo Fam Zheng
2013-10-11 8:31 ` [Qemu-devel] [PATCH v2 2/2] vmdk: implment bdrv_get_specific_info Fam Zheng
2013-10-11 11:52 ` Eric Blake
2013-10-11 12:07 ` Fam Zheng
2013-10-11 12:27 ` Max Reitz [this message]
2013-10-11 11:31 ` [Qemu-devel] [PATCH v2 0/2] vmdk: Implement bdrv_get_specific_info 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=5257EECE.6060809@redhat.com \
--to=mreitz@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@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).