From: Anthony Liguori <anthony@codemonkey.ws>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PULL 00/10] Block patches
Date: Thu, 04 Nov 2010 08:23:09 -0500 [thread overview]
Message-ID: <4CD2B3BD.7010809@codemonkey.ws> (raw)
In-Reply-To: <1288876539-8300-1-git-send-email-kwolf@redhat.com>
On 11/04/2010 08:15 AM, Kevin Wolf wrote:
> The following changes since commit 5fc9cfedfa09199e10b5f9b67dcd286bfeae4f7a:
>
> Fold send_all() wrapper unix_write() into one function (2010-11-03 12:48:09 -0500)
>
> are available in the git repository at:
> git://repo.or.cz/qemu/kevin.git for-anthony
>
> Blue Swirl (1):
> block: avoid a warning on 64 bit hosts with long as int64_t
>
> Kevin Wolf (9):
> scsi-disk: Implement rerror option
> block: Allow bdrv_flush to return errors
> scsi-disk: Complete failed requests in scsi_disk_emulate_command
> scsi-disk: Implement werror for flushes
> vpc: Implement bdrv_flush
> qcow2: Invalidate cache after failed read
> ide: Handle immediate bdrv_aio_flush failure
> virtio-blk: Handle immediate flush failure properly
> scsi-disk: Fix immediate failure of bdrv_aio_*
>
Pulled. Thanks.
Regards,
Anthony Liguori
> block.c | 21 ++++++-
> block.h | 2 +-
> block/blkdebug.c | 4 +-
> block/blkverify.c | 8 +-
> block/cow.c | 4 +-
> block/qcow.c | 4 +-
> block/qcow2-cluster.c | 1 +
> block/qcow2-refcount.c | 1 +
> block/qcow2.c | 4 +-
> block/raw-posix.c | 4 +-
> block/raw-win32.c | 9 +++-
> block/raw.c | 4 +-
> block/vdi.c | 4 +-
> block/vmdk.c | 4 +-
> block/vpc.c | 21 ++++---
> block_int.h | 2 +-
> blockdev.c | 6 +-
> hw/ide/core.c | 12 +++-
> hw/scsi-disk.c | 147 +++++++++++++++++++++++++++++++----------------
> hw/virtio-blk.c | 2 +-
> 20 files changed, 172 insertions(+), 92 deletions(-)
>
prev parent reply other threads:[~2010-11-04 13:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 13:15 [Qemu-devel] [PULL 00/10] Block patches Kevin Wolf
2010-11-04 13:15 ` [Qemu-devel] [PATCH 01/10] scsi-disk: Implement rerror option Kevin Wolf
2010-11-04 13:15 ` [Qemu-devel] [PATCH 02/10] block: Allow bdrv_flush to return errors Kevin Wolf
2010-11-04 13:15 ` [Qemu-devel] [PATCH 03/10] scsi-disk: Complete failed requests in scsi_disk_emulate_command Kevin Wolf
2011-05-16 11:23 ` [Qemu-devel] [regression] qemu-system-arm: segfault in lsi_do_command Jonathan Nieder
2011-05-16 15:13 ` Kevin Wolf
2011-05-16 15:30 ` Jonathan Nieder
2011-05-16 15:43 ` Jonathan Nieder
2011-05-16 15:58 ` Kevin Wolf
2011-05-16 16:26 ` Paolo Bonzini
2011-05-16 18:35 ` Jonathan Nieder
2011-05-17 7:43 ` Kevin Wolf
2010-11-04 13:15 ` [Qemu-devel] [PATCH 04/10] scsi-disk: Implement werror for flushes Kevin Wolf
2010-11-04 13:15 ` [Qemu-devel] [PATCH 05/10] vpc: Implement bdrv_flush Kevin Wolf
2010-11-04 13:15 ` [Qemu-devel] [PATCH 06/10] qcow2: Invalidate cache after failed read Kevin Wolf
2010-11-04 13:15 ` [Qemu-devel] [PATCH 07/10] block: avoid a warning on 64 bit hosts with long as int64_t Kevin Wolf
2010-11-04 13:15 ` [Qemu-devel] [PATCH 08/10] ide: Handle immediate bdrv_aio_flush failure Kevin Wolf
2010-11-04 13:15 ` [Qemu-devel] [PATCH 09/10] virtio-blk: Handle immediate flush failure properly Kevin Wolf
2010-11-04 13:15 ` [Qemu-devel] [PATCH 10/10] scsi-disk: Fix immediate failure of bdrv_aio_* Kevin Wolf
2010-11-04 13:23 ` Anthony Liguori [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=4CD2B3BD.7010809@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kwolf@redhat.com \
--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).