From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
phrdina@redhat.com, stefanha@gmail.com, qemu-devel@nongnu.org,
armbru@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH V3 0/4] qapi and snapshot code clean up in block layer
Date: Mon, 03 Jun 2013 10:22:18 +0800 [thread overview]
Message-ID: <51ABFDDA.8080209@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130531091932.61d4cc03@redhat.com>
于 2013-5-31 21:19, Luiz Capitulino 写道:
> On Fri, 31 May 2013 21:04:10 +0800
> Wenchao Xia <xiawenc@linux.vnet.ibm.com> wrote:
>
>> 于 2013-5-30 10:41, Wenchao Xia 写道:
>>> 于 2013-5-27 23:41, Kevin Wolf 写道:
>>>> Am 25.05.2013 um 05:09 hat Wenchao Xia geschrieben:
>>>>> These patches are the common part of my hmp/qmp block query series
>>>>> and Pavel's
>>>>> qmp snapshot command converion series. It mainly does following things:
>>>>> 1 move snapshot related code to block/snapshot.c, qmp and info
>>>>> dumping code to
>>>>> block/qapi.c.
>>>>> 2 better info dumping function to get rid of buffer, avoid string
>>>>> truncation.
>>>>
>>>> Posted comments on patch 1 and 4.
>>>>
>>>> Patches 2 and 3 are:
>>>> Reviewed-by: Kevin Wolf <kwolf@redhat.com>
>>>>
>>> It seems nothing need change, Kevin, do you think it can be merged?
>>>
>> This serial blocks mine and Pavel's work, anything need to be
>> improved? Respin with
>> -typedef int (*fprintf_function)(FILE *f, const char *fmt, ...)
>> +typedef int (*fprintf_function)(void *out, const char *fmt, ...)
>> ?
>
> As far as my review is concerned, I'm OK with your current version.
>
Thanks Luiz. This series does code moves, so it have big chance to get
conflict when upstream changes, hope it not hang out too long... sorry
for pushing many times.
--
Best Regards
Wenchao Xia
next prev parent reply other threads:[~2013-06-03 2:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 3:09 [Qemu-devel] [PATCH V3 0/4] qapi and snapshot code clean up in block layer Wenchao Xia
2013-05-25 3:09 ` [Qemu-devel] [PATCH V3 1/4] block: drop bs_snapshots global variable Wenchao Xia
2013-05-27 15:18 ` Kevin Wolf
2013-05-28 2:20 ` Wenchao Xia
2013-05-27 15:25 ` Kevin Wolf
2013-05-28 2:24 ` Wenchao Xia
2013-05-28 7:46 ` Stefan Hajnoczi
2013-05-29 7:54 ` Wenchao Xia
2013-05-29 9:09 ` Stefan Hajnoczi
2013-05-29 9:45 ` Wenchao Xia
2013-05-25 3:09 ` [Qemu-devel] [PATCH V3 2/4] block: move snapshot code in block.c to block/snapshot.c Wenchao Xia
2013-05-25 12:17 ` Eric Blake
2013-05-25 3:09 ` [Qemu-devel] [PATCH V3 3/4] block: move qmp and info dump related code to block/qapi.c Wenchao Xia
2013-05-25 3:09 ` [Qemu-devel] [PATCH V3 4/4] block: dump snapshot and image info to specified output Wenchao Xia
2013-05-25 12:15 ` Eric Blake
2013-05-27 15:02 ` Luiz Capitulino
2013-05-27 15:40 ` Kevin Wolf
2013-05-27 15:55 ` Luiz Capitulino
2013-05-28 2:09 ` Wenchao Xia
2013-05-27 15:41 ` [Qemu-devel] [PATCH V3 0/4] qapi and snapshot code clean up in block layer Kevin Wolf
2013-05-30 2:41 ` Wenchao Xia
2013-05-31 13:04 ` Wenchao Xia
2013-05-31 13:19 ` Luiz Capitulino
2013-06-03 2:22 ` Wenchao Xia [this message]
2013-06-04 12:46 ` 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=51ABFDDA.8080209@linux.vnet.ibm.com \
--to=xiawenc@linux.vnet.ibm.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=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.