virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: gaowanlong@cn.fujitsu.com
Cc: linux-scsi@vger.kernel.org, kvm@vger.kernel.org, mst@redhat.com,
	linux-kernel@vger.kernel.org, JBottomley@parallels.com,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH V6 5/5] virtio-scsi: reset virtqueue affinity when doing cpu hotplug
Date: Sat, 23 Mar 2013 07:36:30 +0100	[thread overview]
Message-ID: <514D4D6E.4000303@redhat.com> (raw)
In-Reply-To: <51496BAF.2030202@cn.fujitsu.com>

Il 20/03/2013 08:56, Wanlong Gao ha scritto:
>> This one does not apply on top of virtio-next + patch 1-4 in this series.
> 
> I'm very sorry.
> 
> This fault is because I modified the 4/5 from 
> "/* if the affinity hint is set for virtqueues */"
> to
> "/* If the affinity hint is set for virtqueues */"
> by hand.
> 
> You can also change "If" to "if" in 5/5 to apply this patch without 3-way merge.

Can you respin?

So we can ask James for his Acked-by and get this merged in the next window.

Paolo

  reply	other threads:[~2013-03-23  6:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20  7:01 [PATCH V6 0/5] virtio-scsi multiqueue Wanlong Gao
2013-03-20  7:01 ` [PATCH V6 1/5] virtio-scsi: redo allocation of target data Wanlong Gao
2013-03-20  7:33   ` Asias He
2013-03-20  7:01 ` [PATCH V6 2/5] virtio-scsi: pass struct virtio_scsi to virtqueue completion function Wanlong Gao
2013-03-20  7:01 ` [PATCH V6 3/5] virtio-scsi: push vq lock/unlock into virtscsi_vq_done Wanlong Gao
2013-03-20  7:01 ` [PATCH V6 4/5] virtio-scsi: introduce multiqueue support Wanlong Gao
2013-03-20 21:22   ` Venkatesh Srinivas
2013-03-20  7:01 ` [PATCH V6 5/5] virtio-scsi: reset virtqueue affinity when doing cpu hotplug Wanlong Gao
2013-03-20  7:24   ` Asias He
2013-03-20  7:33     ` Wanlong Gao
2013-03-20  7:56     ` Wanlong Gao
2013-03-23  6:36       ` Paolo Bonzini [this message]
2013-03-23 11:16         ` Wanlong Gao

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=514D4D6E.4000303@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=JBottomley@parallels.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=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).