From: Stefan Hajnoczi <stefanha@gmail.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: kwolf@redhat.com, phrdina@redhat.com, armbru@redhat.com,
qemu-devel@nongnu.org, lcapitulino@redhat.com,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH V13 3/6] qmp: add recursive member in ImageInfo
Date: Wed, 5 Jun 2013 12:56:52 +0200 [thread overview]
Message-ID: <20130605105652.GA30326@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <51A2B6DB.5030206@linux.vnet.ibm.com>
On Mon, May 27, 2013 at 09:28:59AM +0800, Wenchao Xia wrote:
> 于 2013-5-26 0:10, Eric Blake 写道:
> >On 05/24/2013 10:24 PM, Wenchao Xia wrote:
> >> void bdrv_query_image_info(BlockDriverState *bs,
> >> ImageInfo **p_info,
> >> Error **errp)
> >>diff --git a/qapi-schema.json b/qapi-schema.json
> >>index ef1f657..a02999d 100644
> >>--- a/qapi-schema.json
> >>+++ b/qapi-schema.json
> >>@@ -236,6 +236,8 @@
> >> #
> >> # @snapshots: #optional list of VM snapshots
> >> #
> >>+# @backing-image: #optional info of the backing image (since 1.6)
> >>+#
> >> # Since: 1.3
> >> #
> >> ##
> >>@@ -245,7 +247,8 @@
> >> '*actual-size': 'int', 'virtual-size': 'int',
> >> '*cluster-size': 'int', '*encrypted': 'bool',
> >> '*backing-filename': 'str', '*full-backing-filename': 'str',
> >>- '*backing-filename-format': 'str', '*snapshots': ['SnapshotInfo'] } }
> >>+ '*backing-filename-format': 'str', '*snapshots': ['SnapshotInfo'],
> >>+ '*backing-image': 'ImageInfo' } }
> >
> >The API change looks fine, except there is no code change to actually
> >populate the new field. This hunk should probably be squashed with the
> >patch that implements the field. Also, are you missing any changes to
> >qmp-commands.hx?
> >
> nop, in next patch qmp-commands.hx parts is added. Just to make
> review easier, after that I am fine to squash them.
The qapi change should be together with the code that implements it. I
need to see the code in order to review the documentation change.
Stefan
next prev parent reply other threads:[~2013-06-05 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 4:24 [Qemu-devel] [PATCH V13 0/6] enhancement for qmp/hmp interfaces of block info Wenchao Xia
2013-05-25 4:24 ` [Qemu-devel] [PATCH V13 1/6] block: add snapshot info query function bdrv_query_snapshot_info_list() Wenchao Xia
2013-05-25 4:24 ` [Qemu-devel] [PATCH V13 2/6] block: add image info query function bdrv_query_image_info() Wenchao Xia
2013-05-25 12:50 ` Eric Blake
2013-05-25 4:24 ` [Qemu-devel] [PATCH V13 3/6] qmp: add recursive member in ImageInfo Wenchao Xia
2013-05-25 16:10 ` Eric Blake
2013-05-27 1:28 ` Wenchao Xia
2013-06-05 10:56 ` Stefan Hajnoczi [this message]
2013-05-25 4:24 ` [Qemu-devel] [PATCH V13 4/6] qmp: add ImageInfo in BlockDeviceInfo used by query-block Wenchao Xia
2013-05-25 4:24 ` [Qemu-devel] [PATCH V13 5/6] hmp: show ImageInfo in 'info block' Wenchao Xia
2013-05-25 4:24 ` [Qemu-devel] [PATCH V13 6/6] hmp: add parameters device and -v for info block Wenchao Xia
2013-06-05 11:06 ` Stefan Hajnoczi
2013-05-25 12:33 ` [Qemu-devel] [PATCH V13 0/6] enhancement for qmp/hmp interfaces of block info Eric Blake
2013-06-05 11:07 ` Stefan Hajnoczi
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=20130605105652.GA30326@stefanha-thinkpad.muc.redhat.com \
--to=stefanha@gmail.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=phrdina@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiawenc@linux.vnet.ibm.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).