From: Kevin Wolf <kwolf@redhat.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: kvm-devel <kvm@vger.kernel.org>, Hannes Reinecke <hare@suse.de>,
qemu-devel <qemu-devel@nongnu.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Paul Brook <paul@codesourcery.com>,
Christoph Hellwig <hch@lst.de>, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] Re: [PATCH 0/2] [scsi-bus]: Changes for PERSISTENT_RESERVE_OUT and MAINTENANCE CDBs v2
Date: Wed, 16 Jun 2010 16:15:34 +0200 [thread overview]
Message-ID: <4C18DC86.3060601@redhat.com> (raw)
In-Reply-To: <1276695761-16588-1-git-send-email-nab@linux-iscsi.org>
Am 16.06.2010 15:42, schrieb Nicholas A. Bellinger:
> From: Nicholas Bellinger <nab@linux-iscsi.org>
>
> Greetings,
>
> Attached is v2 for a series containing a handful of changes required for scsi-bus in order
> to get PERSISTENT_RESERVE_OUT and MAINTENANCE CDBs working as expected. Thanks to Kevin Wolf
> for pointing out the unnecessary SCSIRequest->cmd.xfer reassignments in scsi_req_length() from
> the original series.
>
> Tested with Linux KVM guests and Megasas 8708EM2 HBA emulation + scsi-generic and
> TCM_Loop target ports.
>
> Signed-off-by: Nicholas A. Bellinger <nab@linux-iscsi.org>
Thanks, applied to the block branch.
One more thing: You usually put things like [scsi-bus] in brackets so
that they are removed by git am. I think this is actually useful
information to have in the commit log, so would you mind leaving the
brackets out for your next submissions?
Kevin
prev parent reply other threads:[~2010-06-16 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 13:42 [Qemu-devel] [PATCH 0/2] [scsi-bus]: Changes for PERSISTENT_RESERVE_OUT and MAINTENANCE CDBs v2 Nicholas A. Bellinger
2010-06-16 14:15 ` 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=4C18DC86.3060601@redhat.com \
--to=kwolf@redhat.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=paul@codesourcery.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).