From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Asias He <asias@redhat.com>
Cc: target-devel@vger.kernel.org, kvm@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>,
seabios@seabios.org, qemu-devel@nongnu.org,
virtualization@lists.linux-foundation.org,
Kevin O'Connor <kevin@koconnor.net>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] Fix booting tcm_vhost + seabios
Date: Mon, 18 Mar 2013 14:26:14 -0700 [thread overview]
Message-ID: <1363641974.3156.59.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <1363311916-23121-1-git-send-email-asias@redhat.com>
On Fri, 2013-03-15 at 09:45 +0800, Asias He wrote:
> Asias He (2):
> virtio-scsi: Set _DRIVER_OK flag before scsi target scanning
> virtio-scsi: Pack struct virtio_scsi_{req_cmd,resp_cmd}
>
> src/virtio-scsi.c | 5 +++--
> src/virtio-scsi.h | 4 ++--
> 2 files changed, 5 insertions(+), 4 deletions(-)
>
Hi Asias,
Thanks for taking the initiative on this, and nice work tracking both of
these stubborn bugs down.
So with these out of the way, we're good to go for an RFC of Paolo's
vhost-scsi-pci code for upstream QEMU, yes..?
I'll have some extra bandwidth this week to spend time on the RFC if
you'd like, otherwise I'm happy with you making the upstream QEMU push
for Paolo's code.
Whatever works best for you. :)
Thank you,
--nab
next prev parent reply other threads:[~2013-03-18 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 1:45 [Qemu-devel] [PATCH 0/2] Fix booting tcm_vhost + seabios Asias He
2013-03-15 1:45 ` [Qemu-devel] [PATCH 1/2] virtio-scsi: Set _DRIVER_OK flag before scsi target scanning Asias He
2013-03-17 9:16 ` Michael S. Tsirkin
2013-03-15 1:45 ` [Qemu-devel] [PATCH 2/2] virtio-scsi: Pack struct virtio_scsi_{req_cmd, resp_cmd} Asias He
2013-03-15 8:15 ` Paolo Bonzini
2013-03-17 9:16 ` Michael S. Tsirkin
2013-03-17 14:28 ` [Qemu-devel] [PATCH 0/2] Fix booting tcm_vhost + seabios Kevin O'Connor
2013-03-18 21:26 ` Nicholas A. Bellinger [this message]
2013-03-19 0:58 ` Asias He
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=1363641974.3156.59.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=asias@redhat.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
--cc=stefanha@redhat.com \
--cc=target-devel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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).