From: Christoph Hellwig <hch@lst.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] block patch queue
Date: Mon, 15 Jun 2009 14:36:08 +0200 [thread overview]
Message-ID: <20090615123607.GA13081@lst.de> (raw)
Hi Anthony,
I've arranged all the pending block patches in a git tree to ease
polling. It's Andrea's important and reviewed aio fix, and the various
host device cleanups from me which haven't gotten a whole lot of
attention unfortunately.
The following changes since commit e19252d32c45e92c919109ec32616382eb2afe6b:
Uri Lublin (1):
migrate_fd_close: delete associated io-handler before closing the fd
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/hch/qemu-block.git master
Andrea Arcangeli (1):
fix qemu_aio_flush
Christoph Hellwig (5):
raw-posix: always store open flags
raw-posix: add a raw_open_common helper
raw-posix: split hdev drivers
block: add bdrv_probe_device method
raw-posix: cleanup ioctl methods
aio.c | 8 +-
block.c | 48 +++--
block/raw-posix.c | 662 ++++++++++++++++++++++++++++------------------------
block/raw-win32.c | 10 +
block_int.h | 5 +
qemu-aio.h | 7 +-
6 files changed, 408 insertions(+), 332 deletions(-)
reply other threads:[~2009-06-15 12:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090615123607.GA13081@lst.de \
--to=hch@lst.de \
--cc=qemu-devel@nongnu.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).