From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <v.sementsov-og@mail.ru>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, eblake@redhat.com,
hreitz@redhat.com, jsnow@redhat.com,
Vladimir Sementsov-Ogievskiy <vsementsov@openvz.org>
Subject: Re: [PATCH v4 0/3] block/dirty-bitmaps: fix and improve bitmap merge
Date: Tue, 24 May 2022 14:47:21 +0200 [thread overview]
Message-ID: <YozT2QIbeYvr/2lu@redhat.com> (raw)
In-Reply-To: <20220517111206.23585-1-v.sementsov-og@mail.ru>
Am 17.05.2022 um 13:12 hat Vladimir Sementsov-Ogievskiy geschrieben:
> From: Vladimir Sementsov-Ogievskiy <vsementsov@openvz.org>
>
> v4:
> 01,03: add Kevin's r-b
> 02: add hbitmap_free() on success patch if local_backup is not needed
>
> Vladimir Sementsov-Ogievskiy (3):
> block: block_dirty_bitmap_merge(): fix error path
> block: improve block_dirty_bitmap_merge(): don't allocate extra bitmap
> block: simplify handling of try to merge different sized bitmaps
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2022-05-24 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 11:12 [PATCH v4 0/3] block/dirty-bitmaps: fix and improve bitmap merge Vladimir Sementsov-Ogievskiy
2022-05-17 11:12 ` [PATCH v4 1/3] block: block_dirty_bitmap_merge(): fix error path Vladimir Sementsov-Ogievskiy
2022-05-17 11:12 ` [PATCH v4 2/3] block: improve block_dirty_bitmap_merge(): don't allocate extra bitmap Vladimir Sementsov-Ogievskiy
2022-05-18 15:30 ` Eric Blake
2022-05-17 11:12 ` [PATCH v4 3/3] block: simplify handling of try to merge different sized bitmaps Vladimir Sementsov-Ogievskiy
2022-05-18 15:32 ` [PATCH v4 0/3] block/dirty-bitmaps: fix and improve bitmap merge Eric Blake
2022-05-24 12:47 ` 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=YozT2QIbeYvr/2lu@redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=v.sementsov-og@mail.ru \
--cc=vsementsov@openvz.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).