linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, linux-kernel@vger.kernel.org
Cc: Zhu Lingshan <lingshan.zhu@intel.com>,
	kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH] vhost/test: fix up after API change
Date: Tue, 9 Jun 2020 13:56:26 +0800	[thread overview]
Message-ID: <8ca24e37-d319-fbf7-0114-ddf7eb110781@redhat.com> (raw)
In-Reply-To: <e747a953-3135-fef9-b098-fca11755d6e4@redhat.com>


On 2020/6/9 下午1:53, Jason Wang wrote:
>
> On 2020/6/8 下午8:42, Michael S. Tsirkin wrote:
>> Pass a flag to request kernel thread use.
>>
>> Fixes: 01fcb1cbc88e ("vhost: allow device that does not depend on 
>> vhost worker")
>> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>> ---
>>   drivers/vhost/test.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/vhost/test.c b/drivers/vhost/test.c
>> index f55cb584b84a..12304eb8da15 100644
>> --- a/drivers/vhost/test.c
>> +++ b/drivers/vhost/test.c
>> @@ -122,7 +122,7 @@ static int vhost_test_open(struct inode *inode, 
>> struct file *f)
>>       vqs[VHOST_TEST_VQ] = &n->vqs[VHOST_TEST_VQ];
>>       n->vqs[VHOST_TEST_VQ].handle_kick = handle_vq_kick;
>>       vhost_dev_init(dev, vqs, VHOST_TEST_VQ_MAX, UIO_MAXIOV + 64,
>> -               VHOST_TEST_PKT_WEIGHT, VHOST_TEST_WEIGHT, NULL);
>> +               VHOST_TEST_PKT_WEIGHT, VHOST_TEST_WEIGHT, true, NULL);
>>         f->private_data = n;
>
>
> Acked-by: Jason Wang <jasowang@redhat.com>
>
> Just to confirm, have you queued the doorbell mapping patches already? 
> Or you expect I squash this into v2 of doorbell mapping series?


Ok, I saw the patches in your linux-next branch.

Thanks


>
> Thanks
>


      reply	other threads:[~2020-06-09  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 12:42 [PATCH] vhost/test: fix up after API change Michael S. Tsirkin
2020-06-09  5:53 ` Jason Wang
2020-06-09  5:56   ` Jason Wang [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=8ca24e37-d319-fbf7-0114-ddf7eb110781@redhat.com \
    --to=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lingshan.zhu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@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).