DPDK website maintenance
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: web@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-web] [PATCH] cleanup supported NICs
Date: Thu, 16 Feb 2017 18:21:59 +0000	[thread overview]
Message-ID: <20170216182159.12528-1-ferruh.yigit@intel.com> (raw)

Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
 doc/nics.html | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/nics.html b/doc/nics.html
index e6d6c4e..dba4cc9 100644
--- a/doc/nics.html
+++ b/doc/nics.html
@@ -62,10 +62,6 @@
 			<ul>
 				<li><a href="/doc/guides/nics/enic.html">enic</a> (UCS Virtual Interface Card)</li>
 			</ul>
-			<h3>Emulex</h3>
-			<ul>
-				<li><a href="/about#6WIND">oce</a> (OneConnect OCe14000 family)</li>
-			</ul>
 			<h3>Intel</h3>
 			<ul>
 				<li><a href="/doc/guides/nics/e1000em.html">e1000</a> (82540, 82545, 82546)</li>
@@ -104,7 +100,6 @@
 					<a href="/doc/guides/nics/vmxnet3.html">vmxnet3 + uio</a>
 					(VMware ESXi)
 				</li>
-				<li><a href="/doc/memnic-pmd">memnic</a></li>
 			</ul>
 			<h3>Others</h3>
 			<ul>
@@ -113,6 +108,11 @@
 				<li><a href="/doc/guides/nics/pcap_ring.html#libpcap-based-pmd">pcap</a> (file or kernel driver)</li>
 				<li><a href="/doc/guides/nics/pcap_ring.html#rings-based-pmd">ring</a> (memory)</li>
 			</ul>
+			<h3>Old</h3>
+			<ul>
+				<li>Emulex: <a href="/about#6WIND">oce</a> (OneConnect OCe14000 family)</li>
+				<li><a href="/doc/memnic-pmd">memnic</a></li>
+			</ul>
 		</section>
 	</body>
 </html>
-- 
2.9.3

             reply	other threads:[~2017-02-16 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 18:21 Ferruh Yigit [this message]
2017-02-26 17:36 ` [dpdk-web] [PATCH v2] " Thomas Monjalon
2017-03-07 14:57   ` Ferruh Yigit
2017-03-07 15:00     ` 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=20170216182159.12528-1-ferruh.yigit@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=thomas.monjalon@6wind.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).