From: Kevin Wolf <kwolf@redhat.com>
To: anthony@codemonkey.ws
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [STABLE PULL 0/6] Block patches for 0.12.x
Date: Fri, 28 May 2010 20:01:26 +0200 [thread overview]
Message-ID: <1275069692-5756-1-git-send-email-kwolf@redhat.com> (raw)
The following changes since commit 0c459361a1117a6c434c7b2b008a4c6c035eb4bf:
Rabin Vincent (1):
arm_timer: fix oneshot mode
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git for-stable-0.12
Kevin Wolf (6):
ide: Fix ide_dma_cancel
qcow2: Clear L2 table cache after write error
qcow2: Fix error handling in l2_allocate
block: Fix multiwrite with overlapping requests
qcow2: Fix corruption after refblock allocation
qcow2: Fix corruption after error in update_refcount
block.c | 2 +-
block/qcow2-cluster.c | 26 +++++++++++++++-----------
block/qcow2-refcount.c | 15 +++++++++++++--
hw/ide/core.c | 8 ++++----
4 files changed, 33 insertions(+), 18 deletions(-)
next reply other threads:[~2010-05-28 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 18:01 Kevin Wolf [this message]
2010-05-28 18:01 ` [Qemu-devel] [STABLE PATCH 1/6] ide: Fix ide_dma_cancel Kevin Wolf
2010-05-28 18:01 ` [Qemu-devel] [STABLE PATCH 2/6] qcow2: Clear L2 table cache after write error Kevin Wolf
2010-05-28 18:01 ` [Qemu-devel] [STABLE PATCH 3/6] qcow2: Fix error handling in l2_allocate Kevin Wolf
2010-05-28 18:01 ` [Qemu-devel] [STABLE PATCH 4/6] block: Fix multiwrite with overlapping requests Kevin Wolf
2010-05-28 18:01 ` [Qemu-devel] [STABLE PATCH 5/6] qcow2: Fix corruption after refblock allocation Kevin Wolf
2010-05-28 18:01 ` [Qemu-devel] [STABLE PATCH 6/6] qcow2: Fix corruption after error in update_refcount Kevin Wolf
2010-06-09 16:41 ` [Qemu-devel] [STABLE PULL 0/6] Block patches for 0.12.x Aurelien Jarno
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=1275069692-5756-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).