All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Lin Ma <lma@suse.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2 V5] Show all of snapshot info on every block dev
Date: Fri, 8 Jul 2016 16:57:57 +0200	[thread overview]
Message-ID: <188a2b20-3c78-731b-c93f-2cbd1a5a2bcb@redhat.com> (raw)
In-Reply-To: <1467869164-26688-1-git-send-email-lma@suse.com>

[-- Attachment #1: Type: text/plain, Size: 743 bytes --]

On 07.07.2016 07:26, Lin Ma wrote:
> V5: Minor changes.
> 
> V4: Use QTAILQ_FOREACH_SAFE instead of QTAILQ_FOREACH while freeing snapshot lists.
> 
> V3: Fix leaking the entries in image_list and the entries in their
>     ImageEntry.snapshots lists
> 
> V2: Split it to 2 patches.
> 
> Lin Ma (2):
>   hmp: use snapshot name to determine whether a snapshot is 'fully
>     available'
>   hmp: show all of snapshot info on every block dev in output of 'info
>     snapshots'
> 
>  migration/savevm.c | 103 ++++++++++++++++++++++++++++++++++++++++++++++++-----
>  1 file changed, 95 insertions(+), 8 deletions(-)

Thanks, I've applied the series to my block branch:

https://github.com/XanClic/qemu/commits/block

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 498 bytes --]

      parent reply	other threads:[~2016-07-08 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07  5:26 [Qemu-devel] [PATCH 0/2 V5] Show all of snapshot info on every block dev Lin Ma
2016-07-07  5:26 ` [Qemu-devel] [PATCH 1/2 V5] hmp: use snapshot name to determine whether a snapshot is 'fully available' Lin Ma
2016-07-07  5:26 ` [Qemu-devel] [PATCH 2/2 V5] hmp: show all of snapshot info on every block dev in output of 'info snapshots' Lin Ma
2016-07-08 14:03   ` Max Reitz
2016-07-08 14:57 ` Max Reitz [this message]

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=188a2b20-3c78-731b-c93f-2cbd1a5a2bcb@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lma@suse.com \
    --cc=qemu-devel@nongnu.org \
    /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.