From: Kevin Wolf <kwolf@redhat.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Christoph Hellwig <hch@lst.de>, Gerd Hoffmann <kraxel@redhat.com>,
Hannes Reinecke <hare@suse.de>, kvm-devel <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
Chris Krumme <chris.krumme@windriver.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] Fix scsi-generic breakage in upstream qemu-kvm.git
Date: Fri, 28 May 2010 13:32:24 +0200 [thread overview]
Message-ID: <4BFFA9C8.3090004@redhat.com> (raw)
In-Reply-To: <1274975788.16907.38.camel@haakon2.linux-iscsi.org>
Am 27.05.2010 17:56, schrieb Nicholas A. Bellinger:
> On Thu, 2010-05-20 at 15:18 +0200, Kevin Wolf wrote:
>> Am 17.05.2010 18:45, schrieb Nicholas A. Bellinger:
>>> From: Nicholas Bellinger <nab@linux-iscsi.org>
>>>
>>> Greetings,
>>>
>>> Attached are the updated patches following hch's comments to fix scsi-generic
>>> device breakage with find_image_format() and refresh_total_sectors().
>>>
>>> These are being resent as the last attachments where in MBOX format from git-format-patch.
>>>
>>> Signed-off-by: Nicholas A. Bellinger <nab@linux-iscsi.org>
>>
>> Thanks, applied all to the block branch, even though I forgot to reply here.
>>
>> Kevin
>
> Hi Kevin,
>
> Thanks for accepting the series. There is one more piece of breakage
> that Chris Krumme found in block.c:find_image_format() in the original
> patch. Please apply the patch to add the missing bdrv_delete() for the
> SG_IO case below.
>
> Thanks for pointing this out Chris!
Right, thanks for the fix. I've applied it to the block branch.
Kevin
prev parent reply other threads:[~2010-05-28 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 16:45 [PATCH 0/2] Fix scsi-generic breakage in upstream qemu-kvm.git Nicholas A. Bellinger
2010-05-20 13:18 ` [Qemu-devel] " Kevin Wolf
2010-05-27 15:56 ` Nicholas A. Bellinger
2010-05-28 11:32 ` Kevin Wolf [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=4BFFA9C8.3090004@redhat.com \
--to=kwolf@redhat.com \
--cc=chris.krumme@windriver.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--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).