qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] ping Re: [PATCH 0/5] My remaining block/SCSI patches for 1.0
Date: Thu, 27 Oct 2011 13:45:29 +0200	[thread overview]
Message-ID: <j8bg8q$uet$2@dough.gmane.org> (raw)
In-Reply-To: <1319540020-32484-1-git-send-email-pbonzini@redhat.com>

On 10/25/2011 12:53 PM, Paolo Bonzini wrote:
> The first three replace patches 20/21 and are basically rewritten with
> input from Kevin.
>
> The fourth is new.  I had it queued for 1.1, but it turns out it is
> needed now or scsi-block might access some requests incorrectly when
> restarting after an error.
>
> The fifth is basically the same as patch 35 from the first submission.
>
> The last three patches had been submitted Sep 20 and were lost at sea;
> support for eject requests is required by udev 173.
>
> Paolo Bonzini (8):
>    scsi: do not call transfer_data after canceling a request
>    scsi-disk: bump SCSIRequest reference count until aio completion runs
>    scsi-generic: bump SCSIRequest reference count until aio completion runs
>    scsi: push request restart to SCSIDevice
>    scsi-disk: add scsi-block for device passthrough
>    block: add eject request callback
>    atapi: implement eject requests
>    scsi-disk: implement eject requests
>
>   block.c           |    7 ++
>   block.h           |    7 ++
>   blockdev.c        |    8 +-
>   hw/ide/atapi.c    |   11 ++-
>   hw/ide/core.c     |   13 +++
>   hw/scsi-bus.c     |   79 ++++++++++++++++-
>   hw/scsi-disk.c    |  254 ++++++++++++++++++++++++++++++++++++++--------------
>   hw/scsi-generic.c |   18 ++++
>   hw/scsi.h         |    6 ++
>   trace-events      |    1 +
>   10 files changed, 325 insertions(+), 79 deletions(-)
>

Ping?

Paolo

      parent reply	other threads:[~2011-10-27 11:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25 10:53 [Qemu-devel] [PATCH 0/5] My remaining block/SCSI patches for 1.0 Paolo Bonzini
2011-10-25 10:53 ` [Qemu-devel] [PATCH 1/8] scsi: do not call transfer_data after canceling a request Paolo Bonzini
2011-10-25 10:53 ` [Qemu-devel] [PATCH 2/8] scsi-disk: bump SCSIRequest reference count until aio completion runs Paolo Bonzini
2011-10-25 10:53 ` [Qemu-devel] [PATCH 3/8] scsi-generic: " Paolo Bonzini
2011-10-25 10:53 ` [Qemu-devel] [PATCH 4/8] scsi: push request restart to SCSIDevice Paolo Bonzini
2011-10-25 10:53 ` [Qemu-devel] [PATCH 5/8] scsi-disk: add scsi-block for device passthrough Paolo Bonzini
2011-10-28 17:04   ` Kevin Wolf
2011-10-25 10:53 ` [Qemu-devel] [PATCH 6/8] block: add eject request callback Paolo Bonzini
2011-10-28 17:21   ` Kevin Wolf
2011-10-29  7:46     ` Paolo Bonzini
2011-11-07 13:21   ` Markus Armbruster
2011-11-07 13:36     ` Paolo Bonzini
2011-11-07 13:49       ` Kevin Wolf
2011-11-07 13:56         ` Paolo Bonzini
2011-11-07 14:12           ` Kevin Wolf
2011-11-07 15:23       ` Markus Armbruster
2011-11-07 16:14         ` Paolo Bonzini
2011-11-07 16:50   ` [Qemu-devel] [PATCH 6/8 v2] " Paolo Bonzini
2011-11-08 13:18     ` Kevin Wolf
2011-10-25 10:53 ` [Qemu-devel] [PATCH 7/8] atapi: implement eject requests Paolo Bonzini
2011-10-25 10:53 ` [Qemu-devel] [PATCH 8/8] scsi-disk: " Paolo Bonzini
2011-10-27 11:45 ` 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='j8bg8q$uet$2@dough.gmane.org' \
    --to=pbonzini@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).