From: Qiming Yang <qiming.yang@intel.com>
To: web@dpdk.org
Cc: john.mcnamara@intel.com, Qiming Yang <qiming.yang@intel.com>
Subject: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs
Date: Wed, 16 May 2018 17:51:30 +0800 [thread overview]
Message-ID: <20180516095130.109867-1-qiming.yang@intel.com> (raw)
Signed-off-by: Qiming Yang <qiming.yang@intel.com>
---
doc/nics.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/nics.html b/doc/nics.html
index ffe4455..58d6bf8 100644
--- a/doc/nics.html
+++ b/doc/nics.html
@@ -75,7 +75,7 @@
<li><a href="/browse/dpdk/tree/drivers/net/e1000/">e1000e</a> (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)</li>
<li><a href="/browse/dpdk/tree/drivers/net/e1000/">igb</a> (82575, 82576, 82580, I210, I211, I350, I354, DH89xx)</li>
<li><a href="/doc/guides/nics/ixgbe.html">ixgbe</a> (82598, 82599, X520, X540, X550)</li>
- <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722)</li>
+ <li><a href="/doc/guides/nics/i40e.html">i40e</a> (X710, XL710, X722, XXV710)</li>
<li><a href="/doc/guides/nics/fm10k.html">fm10k</a> (FM10420)</li>
</ul>
<p>Note: The drivers <em>e1000</em> and <em>e1000e</em> are also called <em>em</em>.
--
2.9.5
next reply other threads:[~2018-05-16 2:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 9:51 Qiming Yang [this message]
2018-05-17 13:15 ` Thomas Monjalon
2018-05-28 21:14 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2018-05-16 2:32 Wenzhuo Lu
2018-05-16 5:50 ` Zhang, Helin
2018-05-16 8:26 ` Mcnamara, John
2018-05-17 13:20 ` Thomas Monjalon
2018-03-21 14:31 Qiming Yang
2018-03-21 8:29 ` Thomas Monjalon
2018-03-21 9:18 ` Mcnamara, John
2018-03-21 9:21 ` Thomas Monjalon
2018-03-21 9:26 ` Mcnamara, John
2018-03-21 9:14 ` Mcnamara, John
2018-03-21 14:25 Qiming Yang
2018-03-21 10:24 Qiming Yang
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=20180516095130.109867-1-qiming.yang@intel.com \
--to=qiming.yang@intel.com \
--cc=john.mcnamara@intel.com \
--cc=web@dpdk.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).