From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qcow2: Keep option in qcow2_invalidate_cache()
Date: Tue, 11 Mar 2014 19:44:34 +0100 [thread overview]
Message-ID: <20140311184434.GA512@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1394556161-16030-1-git-send-email-kwolf@redhat.com>
On Tue, Mar 11, 2014 at 05:42:41PM +0100, Kevin Wolf wrote:
> Instead of manually building a list of all options from BDRVQcowState
> values just reuse the options that were used to open the image.
> qcow2_open() won't fully use all of the options in the QDict, but that's
> okay.
>
> This fixes all of the driver-specific options in qcow2, except for
> lazy-refcounts, which was special cased before.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> block/qcow2.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
prev parent reply other threads:[~2014-03-11 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 16:42 [Qemu-devel] [PATCH] qcow2: Keep option in qcow2_invalidate_cache() Kevin Wolf
2014-03-11 18:32 ` Max Reitz
2014-03-11 18:44 ` Stefan Hajnoczi [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=20140311184434.GA512@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).