DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Stephen Hurd <stephen.hurd@broadcom.com>,
	Rasesh Mody <rasesh.mody@qlogic.com>,
	Harish Patil <harish.patil@qlogic.com>,
	Sony Chacko <sony.chacko@qlogic.com>
Cc: web@dpdk.org
Subject: [dpdk-web] [PATCH] add bnxt and qede in list of supported NICs
Date: Wed, 27 Jul 2016 18:46:54 +0200	[thread overview]
Message-ID: <1469638014-1704-1-git-send-email-thomas.monjalon@6wind.com> (raw)

Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
 doc/nics.html | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/doc/nics.html b/doc/nics.html
index d2b6df7..2e9c600 100644
--- a/doc/nics.html
+++ b/doc/nics.html
@@ -42,6 +42,10 @@
 			<ul>
 				<li><a href="/doc/guides/nics/ena.html">ena</a> (Elastic Network Adapter)</li>
 			</ul>
+			<h3>Broadcom</h3>
+			<ul>
+				<li><a href="/doc/guides/nics/bnxt.html">bnxt</a> (NetXtreme C-Series)</li>
+			</ul>
 			<h3>Cavium</h3>
 			<ul>
 				<li><a href="/doc/guides/nics/thunderx.html">thunderx</a> (CN88XX)</li>
@@ -84,7 +88,8 @@
 			</ul>
 			<h3>QLogic</h3>
 			<ul>
-				<li><a href="/doc/guides/nics/bnx2x.html">bnx2x</a> (QLogic 578xx)</li>
+				<li><a href="/doc/guides/nics/bnx2x.html">bnx2x</a> (578xx)</li>
+				<li><a href="/doc/guides/nics/qede.html">qede</a> (FastLinQ QL4xxxx)</li>
 			</ul>
 			<h3>Paravirtualization</h3>
 			<ul>
-- 
2.7.0

             reply	other threads:[~2016-07-27 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 16:46 Thomas Monjalon [this message]
2016-07-27 20:59 ` Ajit Khaparde
2016-07-28  7:14   ` Thomas Monjalon
2016-07-28 18:36     ` Thomas Monjalon
2016-07-28 18:39       ` Ajit Khaparde
2016-07-28 19:31       ` Ajit Khaparde
2016-07-28 20:09         ` Thomas Monjalon
2016-07-28  7:20 ` Harish Patil

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=1469638014-1704-1-git-send-email-thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=harish.patil@qlogic.com \
    --cc=rasesh.mody@qlogic.com \
    --cc=sony.chacko@qlogic.com \
    --cc=stephen.hurd@broadcom.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).