From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com,
qemu-devel@nongnu.org, qemu-stable@nongnu.org, mreitz@redhat.com,
den@openvz.org, jsnow@redhat.com
Subject: [Qemu-devel] [PATCH v12 0/2] backup: copy_range fixes
Date: Tue, 17 Sep 2019 19:07:29 +0300 [thread overview]
Message-ID: <20190917160731.10895-1-vsementsov@virtuozzo.com> (raw)
Hi all!
Here are two small fixes. They fixes old commit, so qemu-stable is in
CC, but actually, I don't think they are critical.
01: is new
02: is just copied from
[PATCH v11 01/14] block/backup: fix backup_cow_with_offload for last cluster
(I only add Fixes: to commit-message)
and this is why I called this v12, to not interfere with previous
emails
I'd prefer this to go through Max's block branch, as Max is reviewing my
backup-top series, which will refer to these patches and seems simpler
to queue them all together.
Vladimir Sementsov-Ogievskiy (2):
block/backup: fix max_transfer handling for copy_range
block/backup: fix backup_cow_with_offload for last cluster
block/backup.c | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
--
2.21.0
next reply other threads:[~2019-09-17 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 16:07 Vladimir Sementsov-Ogievskiy [this message]
2019-09-17 16:07 ` [Qemu-devel] [PATCH v12 1/2] block/backup: fix max_transfer handling for copy_range Vladimir Sementsov-Ogievskiy
2019-09-18 19:57 ` John Snow
2019-09-19 6:50 ` Vladimir Sementsov-Ogievskiy
2019-09-20 1:13 ` John Snow
2019-09-20 7:52 ` Vladimir Sementsov-Ogievskiy
2019-09-17 16:07 ` [Qemu-devel] [PATCH v12 2/2] block/backup: fix backup_cow_with_offload for last cluster Vladimir Sementsov-Ogievskiy
2019-09-18 20:14 ` John Snow
2019-09-19 7:02 ` Vladimir Sementsov-Ogievskiy
2019-09-20 0:55 ` John Snow
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=20190917160731.10895-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).