From: Max Reitz <mreitz@redhat.com>
To: Ren Kimura <rkx1209dev@gmail.com>
Cc: kwolf@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5] qemu-img: check block status of backing file when converting.
Date: Wed, 27 Apr 2016 18:31:46 +0200 [thread overview]
Message-ID: <5720E972.5050002@redhat.com> (raw)
In-Reply-To: <1461773098-20356-1-git-send-email-rkx1209dev@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 473 bytes --]
On 27.04.2016 18:04, Ren Kimura wrote:
> When converting images, check the block status of its backing file chain
> to avoid needlessly reading zeros.
>
> Signed-off-by: Ren Kimura <rkx1209dev@gmail.com>
> ---
> qemu-img.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
Thank you, I applied the patch to my block-next tree for inclusion into
qemu after the 2.6 release:
https://github.com/XanClic/qemu/commits/block-next
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-04-27 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 16:04 [Qemu-devel] [PATCH v5] qemu-img: check block status of backing file when converting Ren Kimura
2016-04-27 16:31 ` 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=5720E972.5050002@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rkx1209dev@gmail.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).