From: "Kadam, Pallavi" <pallavi.kadam@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, ranjit.menon@intel.com, beilei.xing@intel.com,
jia.guo@intel.com, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: update i40e PMD to support on windows
Date: Fri, 22 Jan 2021 19:29:13 +0530 [thread overview]
Message-ID: <2084015a-8806-99a6-ff4f-d12659f34d24@intel.com> (raw)
In-Reply-To: <16612096.mfC2Pr7Dke@thomas>
On 1/22/2021 3:16 AM, Thomas Monjalon wrote:
> 21/01/2021 20:09, Pallavi Kadam:
>> Add documentation to support i40e PMD on Windows.
>> Update the release notes for the same.
>>
>> Signed-off-by: Pallavi Kadam <pallavi.kadam@intel.com>
>> Reviewed-by: Ranjit Menon <ranjit.menon@intel.com>
>> ---
>> doc/guides/nics/i40e.rst | 16 ++++++++++++++--
>> doc/guides/rel_notes/release_21_02.rst | 4 ++++
>> 2 files changed, 18 insertions(+), 2 deletions(-)
> The update of doc/guides/nics/features/i40e.ini is missing.
> Please see the line "Windows" in mlx5.ini for comparison.
Thank you. Sure, I'll update it in v2.
>
> [...]
>> +- To access any Intel® Ethernet hardware, load the UIO driver in place of existing built-in (inbox) driver.
>> +
>> +- To load UIO driver, follow the steps mentioned in `dpdk-kmods repository
>> + <https://browse.dpdk.org/dpdk-kmods/commit/?id=e28aabd882798f21b94918d4517621ce9e355269>`_.
> I think we should say NetUIO instead of UIO.
Agree. Will replace this in v2.
>
>
next prev parent reply other threads:[~2021-01-22 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 19:09 Pallavi Kadam
2021-01-21 21:46 ` Thomas Monjalon
2021-01-22 13:59 ` Kadam, Pallavi [this message]
2021-01-26 23:03 ` [dpdk-dev] [PATCH v2] " Pallavi Kadam
2021-02-02 12:21 ` Ferruh Yigit
2021-02-02 17:51 ` Kadam, Pallavi
2021-02-02 19:09 ` [dpdk-dev] [PATCH v3] " Pallavi Kadam
2021-02-03 10:22 ` Ferruh Yigit
2021-02-03 10:59 ` Ferruh Yigit
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=2084015a-8806-99a6-ff4f-d12659f34d24@intel.com \
--to=pallavi.kadam@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jia.guo@intel.com \
--cc=ranjit.menon@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).