From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com,
wencongyang2@huawei.com, xiechanglong.d@gmail.com,
armbru@redhat.com, mreitz@redhat.com, den@openvz.org,
jsnow@redhat.com
Subject: [Qemu-devel] [PATCH 0/4] block: drop bs->job
Date: Thu, 6 Jun 2019 18:41:28 +0300 [thread overview]
Message-ID: <20190606154132.153330-1-vsementsov@virtuozzo.com> (raw)
Hi all!
These series follow Kevin's suggestions under
https://lists.gnu.org/archive/html/qemu-devel/2019-06/msg00670.html
[Qemu-devel] [PATCH v2 0/2] introduce pinned blk
(hope you don't mind me using exactly your wording in 02)
Vladimir Sementsov-Ogievskiy (4):
block/replication: drop usage of bs->job
block/block-backend: blk_iostatus_reset: drop usage of bs->job
blockdev: blockdev_mark_auto_del: drop usage of bs->job
block: drop bs->job
include/block/block_int.h | 15 ++++++---------
include/block/blockjob.h | 9 +++++++++
block.c | 2 --
block/block-backend.c | 4 ----
block/mirror.c | 38 ++++++++++++++++++++++----------------
block/replication.c | 21 ++++++++++++---------
blockdev.c | 19 +++++++++----------
blockjob.c | 22 ++++++++++++++--------
qmp.c | 5 +++++
block/trace-events | 2 +-
10 files changed, 78 insertions(+), 59 deletions(-)
--
2.18.0
next reply other threads:[~2019-06-06 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 15:41 Vladimir Sementsov-Ogievskiy [this message]
2019-06-06 15:41 ` [Qemu-devel] [PATCH 1/4] block/replication: drop usage of bs->job Vladimir Sementsov-Ogievskiy
2019-06-06 15:41 ` [Qemu-devel] [PATCH 2/4] block/block-backend: blk_iostatus_reset: " Vladimir Sementsov-Ogievskiy
2019-06-06 15:41 ` [Qemu-devel] [PATCH 3/4] blockdev: blockdev_mark_auto_del: " Vladimir Sementsov-Ogievskiy
2019-06-06 15:41 ` [Qemu-devel] [PATCH 4/4] block: drop bs->job Vladimir Sementsov-Ogievskiy
2019-06-17 16:58 ` Kevin Wolf
2019-06-18 6:53 ` Vladimir Sementsov-Ogievskiy
2019-06-06 16:37 ` [Qemu-devel] [PATCH 0/4] " no-reply
2019-06-14 10:17 ` Kevin Wolf
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=20190606154132.153330-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.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=wencongyang2@huawei.com \
--cc=xiechanglong.d@gmail.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).