From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
pingfank@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 00/17] aio: drop io_flush()
Date: Wed, 17 Apr 2013 15:20:54 +0200 [thread overview]
Message-ID: <516EA1B6.2060401@redhat.com> (raw)
In-Reply-To: <1366204073-8468-1-git-send-email-stefanha@redhat.com>
Il 17/04/2013 15:07, Stefan Hajnoczi ha scritto:
> Part 4 - remove io_flush arguments from aio functions
>
> The big, mechanical patch that drops the io_flush argument:
>
> 16 tests: drop event_active_cb()
Not really. :)
> Note that I split Part 3 from Part 4 so it's easy to review individual block
> drivers.
Great work!
Paolo
prev parent reply other threads:[~2013-04-17 13:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 13:07 [Qemu-devel] [PATCH v2 00/17] aio: drop io_flush() Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 01/17] block: stop relying on io_flush() in bdrv_drain_all() Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 02/17] dataplane/virtio-blk: check exit conditions before aio_poll() Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 03/17] tests: adjust test-aio to new aio_poll() semantics Stefan Hajnoczi
2013-04-17 13:12 ` Paolo Bonzini
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 04/17] tests: adjust test-thread-pool " Stefan Hajnoczi
2013-04-17 13:12 ` Paolo Bonzini
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 05/17] aio: stop using .io_flush() Stefan Hajnoczi
2013-04-17 13:20 ` Paolo Bonzini
2013-04-17 14:53 ` Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 06/17] block/curl: drop curl_aio_flush() Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 07/17] block/gluster: drop qemu_gluster_aio_flush_cb() Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 08/17] block/iscsi: drop iscsi_process_flush() Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 09/17] block/linux-aio: drop qemu_laio_completion_cb() Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 10/17] block/nbd: drop nbd_have_request() Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 11/17] block/rbd: drop qemu_rbd_aio_flush_cb() Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 12/17] block/sheepdog: drop have_co_req() and aio_flush_request() Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 13/17] block/ssh: drop return_true() Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 14/17] dataplane/virtio-blk: drop flush_true() and flush_io() Stefan Hajnoczi
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 15/17] thread-pool: drop thread_pool_active() Stefan Hajnoczi
2013-04-17 13:13 ` Paolo Bonzini
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 16/17] tests: drop event_active_cb() Stefan Hajnoczi
2013-04-17 13:13 ` Paolo Bonzini
2013-04-17 13:07 ` [Qemu-devel] [PATCH v2 17/17] aio: drop io_flush argument Stefan Hajnoczi
2013-04-17 13:15 ` Paolo Bonzini
2013-04-17 14:56 ` Stefan Hajnoczi
2013-04-17 13:20 ` Paolo Bonzini [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=516EA1B6.2060401@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=pingfank@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).