From: "Zhu, Lingshan" <lingshan.zhu@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/3] vDPA/ifcvf: enable virtio-net on Intel F2000X-PL
Date: Mon, 12 Jun 2023 14:37:36 +0800 [thread overview]
Message-ID: <e8bea552-8d63-a3cb-b8fb-061ca0c57750@intel.com> (raw)
In-Reply-To: <20230609121512-mutt-send-email-mst@kernel.org>
On 6/10/2023 12:15 AM, Michael S. Tsirkin wrote:
> On Sat, Jun 10, 2023 at 12:21:57AM +0800, Zhu Lingshan wrote:
>> Hi
>>
>> This series enables vDPA/ifcvf support for virtio-net devices
>> on Intel F2000X-PL Infrastructure Processing Unit.
>>
>> Please help review
>
> Hard trouble applying - which tree is this against?
Linus tree. I will rebase this series on your tree soon, linux-next branch,
with some minor improvements.
Thanks
>
>> Thanks!
>>
>> Zhu Lingshan (3):
>> vDPA/ifcvf: dynamic allocate vq data stores
>> vDPA/ifcvf: detect and report max allowed vq size
>> vDPA/ifcvf: implement new accessors for vq_state
>>
>> drivers/vdpa/ifcvf/ifcvf_base.c | 55 +++++++++++++++++++++++----------
>> drivers/vdpa/ifcvf/ifcvf_base.h | 26 +++++++---------
>> drivers/vdpa/ifcvf/ifcvf_main.c | 10 ++++--
>> 3 files changed, 58 insertions(+), 33 deletions(-)
>>
>> --
>> 2.39.1
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2023-06-12 6:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 16:21 [PATCH 0/3] vDPA/ifcvf: enable virtio-net on Intel F2000X-PL Zhu Lingshan
2023-06-09 16:15 ` Michael S. Tsirkin
2023-06-12 6:37 ` Zhu, Lingshan [this message]
2023-06-09 16:21 ` [PATCH 1/3] vDPA/ifcvf: dynamic allocate vq data stores Zhu Lingshan
2023-06-09 16:21 ` [PATCH 2/3] vDPA/ifcvf: detect and report max allowed vq size Zhu Lingshan
2023-06-09 16:22 ` [PATCH 3/3] vDPA/ifcvf: implement new accessors for vq_state Zhu Lingshan
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=e8bea552-8d63-a3cb-b8fb-061ca0c57750@intel.com \
--to=lingshan.zhu@intel.com \
--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).