From: Kevin Wolf <kwolf@redhat.com>
To: Edgar Kaziakhmedov <edgar.kaziakhmedov@virtuozzo.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, mreitz@redhat.com,
vsementsov@virtuozzo.com, den@openvz.org,
klim.kireev@virtuozzo.com
Subject: Re: [Qemu-devel] [PATCH] qcow2: get rid of qcow2_backing_read1 routine
Date: Wed, 13 Dec 2017 11:41:32 +0100 [thread overview]
Message-ID: <20171213104132.GB3950@localhost.localdomain> (raw)
In-Reply-To: <20171212144054.16955-1-edgar.kaziakhmedov@virtuozzo.com>
Am 12.12.2017 um 15:40 hat Edgar Kaziakhmedov geschrieben:
> Since bdrv_co_preadv does all neccessary checks including
> reading after the end of the backing file, avoid duplication
> of verification before bdrv_co_preadv call.
>
> Signed-off-by: Edgar Kaziakhmedov <edgar.kaziakhmedov@virtuozzo.com>
> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Thanks, applied to block-next.
Kevin
prev parent reply other threads:[~2017-12-13 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 14:40 [Qemu-devel] [PATCH] qcow2: get rid of qcow2_backing_read1 routine Edgar Kaziakhmedov
2017-12-12 22:22 ` Eric Blake
2017-12-13 10:41 ` Kevin Wolf [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=20171213104132.GB3950@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=den@openvz.org \
--cc=edgar.kaziakhmedov@virtuozzo.com \
--cc=klim.kireev@virtuozzo.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).