From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, Kevin Wolf <kwolf@redhat.com>
Cc: pkrempa@redhat.com, Eduardo Habkost <ehabkost@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Markus Armbruster <armbru@redhat.com>,
vsementsov@virtuozzo.com, Cleber Rosa <crosa@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH RFC v2 1/5] block: add bitmap-populate job
Date: Tue, 16 Jun 2020 15:51:08 -0400 [thread overview]
Message-ID: <2b3b7915-8c88-8cb5-25d7-f99a5f1832db@redhat.com> (raw)
In-Reply-To: <bb9a31cf-99e0-ef35-3739-bb3ff270735d@redhat.com>
On 6/16/20 3:46 PM, Eric Blake wrote:
> I'm less certain what the BLOCK_OP_TYPE_* constants are supposed to
> block, or if this is just copy/paste from backup.c. Does BlockOpType in
> block.h need a new entry?
Copy paste. I wasn't sure myself.
next prev parent reply other threads:[~2020-06-16 19:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 3:49 [PATCH RFC v2 0/5] block: add block-dirty-bitmap-populate job John Snow
2020-05-14 3:49 ` [PATCH RFC v2 1/5] block: add bitmap-populate job John Snow
2020-05-18 20:49 ` Eric Blake
2020-05-19 8:27 ` Peter Krempa
2020-06-04 9:12 ` Kevin Wolf
2020-06-04 9:16 ` Peter Krempa
2020-06-04 11:31 ` Kevin Wolf
2020-06-04 16:22 ` Peter Krempa
2020-06-05 9:01 ` Kevin Wolf
2020-06-05 9:24 ` Peter Krempa
2020-06-05 9:44 ` Kevin Wolf
2020-06-05 9:58 ` Peter Krempa
2020-06-05 10:07 ` Kevin Wolf
2020-06-05 10:59 ` Peter Krempa
2020-06-06 6:55 ` Vladimir Sementsov-Ogievskiy
2020-06-08 9:21 ` Kevin Wolf
2020-06-08 10:00 ` Vladimir Sementsov-Ogievskiy
2020-06-08 13:15 ` Kevin Wolf
2020-06-08 9:38 ` Peter Krempa
2020-06-08 10:30 ` Vladimir Sementsov-Ogievskiy
2020-06-08 12:01 ` Peter Krempa
2020-06-04 9:01 ` Kevin Wolf
2020-06-16 19:46 ` Eric Blake
2020-06-16 19:51 ` John Snow [this message]
2020-06-16 20:02 ` Eric Blake
2020-06-17 10:57 ` Kevin Wolf
2020-05-14 3:49 ` [PATCH RFC v2 2/5] blockdev: combine DriveBackupState and BlockdevBackupState John Snow
2020-05-18 20:57 ` Eric Blake
2020-05-14 3:49 ` [PATCH RFC v2 3/5] qmp: expose block-dirty-bitmap-populate John Snow
2020-05-18 21:10 ` Eric Blake
2020-05-14 3:49 ` [PATCH RFC v2 4/5] iotests: move bitmap helpers into their own file John Snow
2020-05-14 3:49 ` [PATCH RFC v2 5/5] iotests: add 287 for block-dirty-bitmap-populate John Snow
2020-05-18 21:22 ` Eric Blake
2020-06-04 9:24 ` Kevin Wolf
2020-05-18 14:52 ` [PATCH RFC v2 0/5] block: add block-dirty-bitmap-populate job Peter Krempa
2020-06-09 15:04 ` Peter Krempa
2020-06-05 21:51 ` Eric Blake
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=2b3b7915-8c88-8cb5-25d7-f99a5f1832db@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkrempa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.