From: Stefan Hajnoczi <stefanha@gmail.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
aliguori@us.ibm.com, Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, lcapitulino@redhat.com,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH V7 09/14] block: move bdrv_snapshot_find() to block.c
Date: Tue, 5 Mar 2013 10:21:05 +0100 [thread overview]
Message-ID: <20130305092105.GB1938@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <51359AB4.4030501@linux.vnet.ibm.com>
On Tue, Mar 05, 2013 at 03:11:48PM +0800, Wenchao Xia wrote:
> 于 2013-3-4 21:02, Stefan Hajnoczi 写道:
> >On Fri, Mar 01, 2013 at 09:51:53AM +0800, Wenchao Xia wrote: > 于 2013-2-28 0:22, Kevin Wolf 写道:
> >>>Am 27.02.2013 um 17:04 hat Markus Armbruster geschrieben:
> >>>>Wenchao Xia <xiawenc@linux.vnet.ibm.com> writes:
> >>>>
> >>>>>Signed-off-by: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
> >>>>>Reviewed-by: Eric Blake <eblake@redhat.com>
> >>>>>---
> >>>>> block.c | 24 ++++++++++++++++++++++++
> >>>>> include/block/block.h | 2 ++
> >>>>> savevm.c | 22 ----------------------
> >>>>> 3 files changed, 26 insertions(+), 22 deletions(-)
> >>>>
> >>>>Perhaps savevm.c isn't the best home for snapshot stuff, but I don't
> >>>>like it in block.c any better. block.c is already unwieldy, and I'd
> >>>>like us to try limiting it to core block stuff.
> >>>>
> >>>>Kevin, Stefan, any ideas?
> >>>
> >>>Take some more snapshot related functions from block.c and move them to
> >>>block/snapshot.c?
> >>>
> >>>Kevin
> >>>
> >>Hi, Stefan
> >> Do you also agree about adding new file block/snapshot.c?
> >
> >Yes, I agree.
> >
> >Stefan
> >
> great. Also there are some other functions such as image info
> collecting, do you think new file block/misc.c is suitable
> to store those functions there?
As discussed on IRC, it's fine by me. If a better way to organize these
functions becomes clear in the future they can be moved.
Stefan
next prev parent reply other threads:[~2013-03-05 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1361875228-15769-1-git-send-email-xiawenc@linux.vnet.ibm.com>
[not found] ` <1361875228-15769-9-git-send-email-xiawenc@linux.vnet.ibm.com>
[not found] ` <878v69hhl5.fsf@blackfin.pond.sub.org>
[not found] ` <512EBD01.8010906@linux.vnet.ibm.com>
2013-03-04 2:30 ` [Qemu-devel] [PATCH V7 08/14] qmp: add interface query-images Wenchao Xia
[not found] ` <1361875228-15769-10-git-send-email-xiawenc@linux.vnet.ibm.com>
[not found] ` <874ngxhhfv.fsf@blackfin.pond.sub.org>
[not found] ` <20130227162229.GJ2514@dhcp-200-207.str.redhat.com>
[not found] ` <513009B9.4090406@linux.vnet.ibm.com>
2013-03-04 3:20 ` [Qemu-devel] [PATCH V7 09/14] block: move bdrv_snapshot_find() to block.c Wenchao Xia
2013-03-04 13:02 ` Stefan Hajnoczi
2013-03-05 7:11 ` Wenchao Xia
2013-03-05 9:21 ` Stefan Hajnoczi [this message]
2013-03-05 10:08 ` Kevin Wolf
2013-03-05 10:52 ` Paolo Bonzini
[not found] ` <20130228155702.GJ18389@stefanha-thinkpad.redhat.com>
[not found] ` <513008B1.8080605@linux.vnet.ibm.com>
2013-03-04 13:10 ` [Qemu-devel] [PATCH V7 00/14] add qmp/hmp interfaces for internal snapshot info Stefan Hajnoczi
2013-03-05 0:43 ` 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=20130305092105.GB1938@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@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).