From: Stefan Hajnoczi <stefanha@gmail.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] block stream: close unused files and update ->backing_hd
Date: Tue, 27 Mar 2012 08:13:51 +0100 [thread overview]
Message-ID: <20120327071351.GC17933@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <20120327002210.GB8343@amt.cnet>
On Mon, Mar 26, 2012 at 09:22:10PM -0300, Marcelo Tosatti wrote:
>
> Close the now unused images that were part of the previous backing file
> chain and adjust ->backing_hd, backing_filename and backing_format
> properly.
>
> Fixes https://bugzilla.redhat.com/show_bug.cgi?id=801449
>
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
next prev parent reply other threads:[~2012-03-27 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 0:22 [Qemu-devel] [PATCH v2] block stream: close unused files and update ->backing_hd Marcelo Tosatti
2012-03-27 7:13 ` Stefan Hajnoczi [this message]
2012-04-05 13:12 ` 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=20120327071351.GC17933@stefanha-thinkpad.localdomain \
--to=stefanha@gmail.com \
--cc=kwolf@redhat.com \
--cc=mtosatti@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).