From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Subject: [Qemu-devel] [PATCH v3 05/15] block: Remove unused typedef of BlockDriverDirtyHandler
Date: Sat, 27 Feb 2016 17:20:47 +0800 [thread overview]
Message-ID: <1456564857-29160-6-git-send-email-famz@redhat.com> (raw)
In-Reply-To: <1456564857-29160-1-git-send-email-famz@redhat.com>
Signed-off-by: Fam Zheng <famz@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
---
include/block/block.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/block/block.h b/include/block/block.h
index 3fbd70d..ff1933a 100644
--- a/include/block/block.h
+++ b/include/block/block.h
@@ -322,8 +322,6 @@ BlockDriverState *check_to_replace_node(BlockDriverState *parent_bs,
const char *node_name, Error **errp);
/* async block I/O */
-typedef void BlockDriverDirtyHandler(BlockDriverState *bs, int64_t sector,
- int sector_num);
BlockAIOCB *bdrv_aio_readv(BlockDriverState *bs, int64_t sector_num,
QEMUIOVector *iov, int nb_sectors,
BlockCompletionFunc *cb, void *opaque);
--
2.4.3
next prev parent reply other threads:[~2016-02-27 9:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 9:20 [Qemu-devel] [PATCH v3 00/15] Dirty bitmap changes for migration/persistence work Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 01/15] backup: Use Bitmap to replace "s->bitmap" Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 02/15] block: Include hbitmap.h in block.h Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 03/15] typedefs: Add BdrvDirtyBitmap Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 04/15] block: Move block dirty bitmap code to separate files Fam Zheng
2016-03-07 18:49 ` [Qemu-devel] [Qemu-block] " Max Reitz
2016-03-08 2:38 ` Fam Zheng
2016-02-27 9:20 ` Fam Zheng [this message]
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 06/15] block: Hide HBitmap in block dirty bitmap interface Fam Zheng
2016-03-07 19:11 ` [Qemu-devel] [Qemu-block] " Max Reitz
2016-03-08 2:14 ` Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 07/15] HBitmap: Introduce "meta" bitmap to track bit changes Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 08/15] tests: Add test code for meta bitmap Fam Zheng
2016-02-29 22:49 ` [Qemu-devel] [Qemu-block] " John Snow
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 09/15] block: Support meta dirty bitmap Fam Zheng
2016-02-29 23:00 ` [Qemu-devel] [Qemu-block] " John Snow
2016-03-08 2:31 ` Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 10/15] block: Add two dirty bitmap getters Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 11/15] block: Assert that bdrv_release_dirty_bitmap succeeded Fam Zheng
2016-02-29 23:05 ` [Qemu-devel] [Qemu-block] " John Snow
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 12/15] hbitmap: serialization Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 13/15] block: BdrvDirtyBitmap serialization interface Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 14/15] tests: Add test code for hbitmap serialization Fam Zheng
2016-02-27 9:20 ` [Qemu-devel] [PATCH v3 15/15] block: More operations for meta dirty bitmap Fam Zheng
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=1456564857-29160-6-git-send-email-famz@redhat.com \
--to=famz@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.