From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Pallavi Kadam <pallavi.kadam@intel.com>
Cc: dev@dpdk.org, thomas@monjalon.net, ranjit.menon@intel.com,
Narcisa.Vasile@microsoft.com, shivanshu.shukla@intel.com
Subject: Re: [dpdk-dev] [PATCH] windows/netuio: add Intel Virtual Function device IDs
Date: Wed, 15 Sep 2021 22:07:37 +0300 [thread overview]
Message-ID: <20210915220737.2c99f5a8@sovereign> (raw)
In-Reply-To: <20210915005137.2186-1-pallavi.kadam@intel.com>
2021-09-14 17:51 (UTC-0700), Pallavi Kadam:
> Add Intel Ethernet Virtual Function device IDs to netuio inf file
> to support Intel 40GbE and 100GbE deives on Windows VM.
Nit: why only VM? Can't VF be used from the host?
>
> Signed-off-by: Pallavi Kadam <pallavi.kadam@intel.com>
> Reviewed-by: Ranjit Menon <ranjit.menon@intel.com>
Acked-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
next prev parent reply other threads:[~2021-09-15 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 0:51 Pallavi Kadam
2021-09-15 19:07 ` Dmitry Kozlyuk [this message]
2021-09-15 20:46 ` Menon, Ranjit
2021-09-30 20:18 ` Thomas Monjalon
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=20210915220737.2c99f5a8@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=Narcisa.Vasile@microsoft.com \
--cc=dev@dpdk.org \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=shivanshu.shukla@intel.com \
--cc=thomas@monjalon.net \
/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).