From: Kevin Wolf <kwolf@redhat.com>
To: anthony@codemonkey.ws
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/5] Block patches for 1.1
Date: Mon, 7 May 2012 19:55:49 +0200 [thread overview]
Message-ID: <1336413354-5244-1-git-send-email-kwolf@redhat.com> (raw)
The following changes since commit 847c25d01cbe8e4fe457a7426f82daaaf3287aae:
hw/ac97: Mask out the EAPD bit on Powerdown Ctrl/Stat writes (2012-05-07 16:31:40 +0400)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git for-anthony
Hervé Poussineau (1):
fdc: simplify media change handling
Kevin Wolf (1):
qcow2: Limit COW to where it's needed
MORITA Kazutaka (1):
sheepdog: switch to writethrough mode if cluster doesn't support flush
Zhi Yong Wu (2):
block: make bdrv_create adopt coroutine
qcow2: lock on prealloc
block.c | 44 ++++++++++++++++++++++++++++++++++++++++++--
block/qcow2-cluster.c | 14 +++++++++-----
block/qcow2.c | 3 +++
block/sheepdog.c | 8 ++++++++
hw/fdc.c | 29 +++++++++++------------------
5 files changed, 73 insertions(+), 25 deletions(-)
next reply other threads:[~2012-05-07 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 17:55 Kevin Wolf [this message]
2012-05-07 17:55 ` [Qemu-devel] [PATCH 1/5] sheepdog: switch to writethrough mode if cluster doesn't support flush Kevin Wolf
2012-05-07 17:55 ` [Qemu-devel] [PATCH 2/5] qcow2: Limit COW to where it's needed Kevin Wolf
2012-05-07 17:55 ` [Qemu-devel] [PATCH 3/5] block: make bdrv_create adopt coroutine Kevin Wolf
2012-05-07 17:55 ` [Qemu-devel] [PATCH 4/5] qcow2: lock on prealloc Kevin Wolf
2012-05-07 17:55 ` [Qemu-devel] [PATCH 5/5] fdc: simplify media change handling Kevin Wolf
2012-05-08 16:11 ` [Qemu-devel] [PULL 0/5] Block patches for 1.1 Anthony Liguori
[not found] <1338385036-9460-1-git-send-email-kwolf@redhat.com>
2012-06-04 5:46 ` Anthony Liguori
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=1336413354-5244-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=anthony@codemonkey.ws \
--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).