From: Rusty Russell <rusty@rustcorp.com.au>
To: Asias He <asias@redhat.com>
Cc: gaowanlong@cn.fujitsu.com, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, linux-scsi@vger.kernel.org,
virtualization@lists.linux-foundation.org, mst@redhat.com,
venkateshs@google.com, pbonzini@redhat.com,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH V7 0/5] virtio-scsi multiqueue
Date: Mon, 08 Apr 2013 23:06:31 +0930 [thread overview]
Message-ID: <878v4t9mao.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20130407020140.GA6409@hj.localdomain>
Asias He <asias@redhat.com> writes:
> On Sat, Apr 06, 2013 at 09:40:13AM +0100, James Bottomley wrote:
>> Well, I haven't had time to look at anything other than the patch I
>> commented on. I'm happy with your fix, so you can add my acked by to
>> that one. Since it's going through the virtio tree, don't wait for me,
>> put it in and I'll make you fix up anything I find later that I'm
>> unhappy with.
>
> So, Rusty, could you pick this up in your virtio-next tree?
Done!
Thanks,
Rusty.
prev parent reply other threads:[~2013-04-08 13:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 11:28 [PATCH V7 0/5] virtio-scsi multiqueue Wanlong Gao
2013-03-23 11:28 ` [PATCH V7 1/5] virtio-scsi: redo allocation of target data Wanlong Gao
2013-03-23 11:28 ` [PATCH V7 2/5] virtio-scsi: pass struct virtio_scsi to virtqueue completion function Wanlong Gao
2013-03-23 11:28 ` [PATCH V7 3/5] virtio-scsi: push vq lock/unlock into virtscsi_vq_done Wanlong Gao
2013-03-23 11:28 ` [PATCH V7 4/5] virtio-scsi: introduce multiqueue support Wanlong Gao
2013-03-25 7:25 ` Bart Van Assche
2013-03-25 14:27 ` Paolo Bonzini
2013-03-23 11:28 ` [PATCH V7 5/5] virtio-scsi: reset virtqueue affinity when doing cpu hotplug Wanlong Gao
2013-03-28 2:22 ` [PATCH V7 0/5] virtio-scsi multiqueue Wanlong Gao
2013-04-05 8:55 ` Wanlong Gao
2013-04-06 8:40 ` James Bottomley
2013-04-06 10:14 ` Wanlong Gao
2013-04-07 2:01 ` Asias He
2013-04-08 13:36 ` Rusty Russell [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=878v4t9mao.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=James.Bottomley@HansenPartnership.com \
--cc=asias@redhat.com \
--cc=gaowanlong@cn.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=venkateshs@google.com \
--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