qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lin Ma <lma@suse.com>
To: mreitz@redhat.com, qemu-devel@nongnu.org
Cc: kwolf@redhat.com
Subject: [Qemu-devel] [PATCH 0/2 V3] Show all of snapshot info on every block dev
Date: Wed, 29 Jun 2016 15:43:11 +0800	[thread overview]
Message-ID: <1467186193-24964-1-git-send-email-lma@suse.com> (raw)

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 | 101 ++++++++++++++++++++++++++++++++++++++++++++++++-----
 1 file changed, 93 insertions(+), 8 deletions(-)

-- 
2.8.1

             reply	other threads:[~2016-06-29  7:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29  7:43 Lin Ma [this message]
2016-06-29  7:43 ` [Qemu-devel] [PATCH 1/2 V3] hmp: use snapshot name to determine whether a snapshot is 'fully available' Lin Ma
2016-07-02 13:26   ` Max Reitz
2016-06-29  7:43 ` [Qemu-devel] [PATCH 2/2 V3] hmp: show all of snapshot info on every block dev in output of 'info snapshots' Lin Ma
2016-07-02 13:34   ` Max Reitz

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=1467186193-24964-1-git-send-email-lma@suse.com \
    --to=lma@suse.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.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 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).