All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	phrdina@redhat.com, famz@redhat.com, qemu-devel@nongnu.org,
	armbru@redhat.com, lcapitulino@redhat.com, stefanha@redhat.com,
	pbonzini@redhat.com, dietmar@proxmox.com
Subject: Re: [Qemu-devel] [PATCH V7 0/8] add internal snapshot support at block device level
Date: Mon, 02 Sep 2013 09:44:31 +0800	[thread overview]
Message-ID: <5223ED7F.8080208@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130816153604.GB24852@stefanha-thinkpad.redhat.com>

于 2013-8-16 23:36, Stefan Hajnoczi 写道:
> On Wed, Aug 07, 2013 at 11:00:11AM +0800, Wenchao Xia wrote:
>> v6:
>>    Address Stefan's comments:
>>    2/8: macro STR_PRINT_CHAR was renamed as STR_OR_NULL, and moved into patch 5,
>> since implement function in this patch do not printf snapshot id any more, as
>> Kevin's suggestion.
>
> Great.
>
>>    Address Kevin's comments:
>>    2/8: remove device, id, name info in the error message, use error message in
>> existing caller. A new function bdrv_snapshot_delete_by_id_or_name() is added
>> to make the usage clear while keep logic unchanged.
>>    3/8: remove device info in error message when name is empty. Use else if
>> after call of bdrv_snapshot_find_by_id_and_name().
>>    Other:
>>    2/8: refined the comments in code for bdrv_snapshot_delete().
>>    3/8: in error reporting, change format from "reason is: '%s'" to
>> "reason is: %s".
>
> Kevin: do you have time to review these changes?
>
> Stefan
>
Hi, Kevin
   Do you have comments for it?

-- 
Best Regards

Wenchao Xia

  reply	other threads:[~2013-09-02  1:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07  3:00 [Qemu-devel] [PATCH V7 0/8] add internal snapshot support at block device level Wenchao Xia
2013-08-07  3:00 ` [Qemu-devel] [PATCH V7 1/8] snapshot: new function bdrv_snapshot_find_by_id_and_name() Wenchao Xia
2013-08-07  3:00 ` [Qemu-devel] [PATCH V7 2/8] snapshot: distinguish id and name in snapshot delete Wenchao Xia
2013-09-10 12:36   ` Kevin Wolf
2013-09-11  2:30     ` Wenchao Xia
2013-08-07  3:00 ` [Qemu-devel] [PATCH V7 3/8] qmp: add internal snapshot support in qmp_transaction Wenchao Xia
2013-08-07  3:00 ` [Qemu-devel] [PATCH V7 4/8] qmp: add interface blockdev-snapshot-internal-sync Wenchao Xia
2013-08-07  3:00 ` [Qemu-devel] [PATCH V7 5/8] qmp: add interface blockdev-snapshot-delete-internal-sync Wenchao Xia
2013-08-07  3:00 ` [Qemu-devel] [PATCH V7 6/8] hmp: add interface hmp_snapshot_blkdev_internal Wenchao Xia
2013-08-07  3:00 ` [Qemu-devel] [PATCH V7 7/8] hmp: add interface hmp_snapshot_delete_blkdev_internal Wenchao Xia
2013-08-07  3:00 ` [Qemu-devel] [PATCH V7 8/8] qemu-iotests: add 057 internal snapshot for block device test case Wenchao Xia
2013-08-16  2:16 ` [Qemu-devel] [PATCH V7 0/8] add internal snapshot support at block device level Wenchao Xia
2013-08-16 15:36 ` Stefan Hajnoczi
2013-09-02  1:44   ` Wenchao Xia [this message]
2013-09-10 12:26 ` Kevin Wolf
2013-09-10 13:09 ` 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=5223ED7F.8080208@linux.vnet.ibm.com \
    --to=xiawenc@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --cc=dietmar@proxmox.com \
    --cc=famz@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 \
    --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 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.