From: "Zhu, Lingshan" <lingshan.zhu@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: jasowang@redhat.com, lingshan.zhu@kernel.org,
virtualization@lists.linux.dev
Subject: Re: [PATCH] MAINTAINERS: Change lingshan's email to kernel.org
Date: Tue, 14 May 2024 09:16:20 +0800 [thread overview]
Message-ID: <efe1f606-11bd-45f6-8e29-7dffb7ca25e9@intel.com> (raw)
In-Reply-To: <20240513093842-mutt-send-email-mst@kernel.org>
On 5/13/2024 9:39 PM, Michael S. Tsirkin wrote:
> On Tue, May 14, 2024 at 05:27:50AM +0800, Zhu Lingshan wrote:
>> This commit changes lingshan's email from intel.com
>> to kernel.org.
>>
>> This commit also changes the title since ifcvf drives
>> standard virtio pci devices now.
>>
>> Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
>> ---
>> MAINTAINERS | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index d75527f7bb0d..b69239cf30a3 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -10465,8 +10465,8 @@ F: include/net/nl802154.h
>> F: net/ieee802154/
>> F: net/mac802154/
>>
>> -Intel VIRTIO DATA PATH ACCELERATOR
>> -M: Zhu Lingshan <lingshan.zhu@intel.com>
>> +Intel AND STANDARD VIRTIO DATA PATH ACCELERATOR
>> +M: Zhu Lingshan <lingshan.zhu@kernel.org>
> Confused. Isn't it still for intel devices?
It still drives Intel devices, however only bar4 is intel specific, all
other
implementations are standard virtio pci.
>
> We have drivers for standard virtio devices already.
yes we have vp_vdpa, but I think no harmful let ifcvf drive also
work for standard virtio pci devices.
>
>
>> L: virtualization@lists.linux.dev
>> S: Supported
>> F: drivers/vdpa/ifcvf/
>> --
>> 2.43.0
prev parent reply other threads:[~2024-05-14 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 21:27 [PATCH] MAINTAINERS: Change lingshan's email to kernel.org Zhu Lingshan
2024-05-13 13:39 ` Michael S. Tsirkin
2024-05-14 1:16 ` Zhu, Lingshan [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=efe1f606-11bd-45f6-8e29-7dffb7ca25e9@intel.com \
--to=lingshan.zhu@intel.com \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).