DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: web@dpdk.org
Subject: [dpdk-web] [PATCH] move unmaintained extensions at the bottom
Date: Fri, 12 Feb 2016 17:41:23 +0100	[thread overview]
Message-ID: <1455295283-18409-1-git-send-email-thomas.monjalon@6wind.com> (raw)

The extensions memnic and vmxnet3 are not maintained and
does not work anymore with the latest DPDK.
Make their status explicit before a possible removal.

Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
 doc.html      |  8 ++------
 download.html | 10 +++++-----
 2 files changed, 7 insertions(+), 11 deletions(-)

diff --git a/doc.html b/doc.html
index 84c596d..397daea 100644
--- a/doc.html
+++ b/doc.html
@@ -53,12 +53,6 @@
 				<li>The guides are also available as
 					<a href="/doc/pdf-guides/">PDF files</a>.
 			</ul>
-			<h3>Extensions</h3>
-			<p>Drivers for paravirtualized NICs:</p>
-			<ul>
-				<li>For QEMU via IVSHMEM, read the <a href="/doc/memnic-pmd">memnic-pmd manual</a>.</li>
-				<li>For VMware ESXi via vmxnet3 without uio, read the <a href="/doc/vmxnet3-usermap">vmxnet3-usermap manual</a>.</li>
-			</ul>
 			<h3>Applications</h3>
 			<ul>
 				<li><a href="http://pktgen.readthedocs.org">pktgen-dpdk (traffic generator)</a>
@@ -70,6 +64,8 @@
 			<h3>Archives</h3>
 			<ul>
 				<li><a href="/doc/archives">documentation for previous versions</a>
+				<li>Unmaintained driver for QEMU IVSHMEM: <a href="/doc/memnic-pmd">memnic-pmd</a>.
+				<li>Unmaintained driver for VMware ESXi vmxnet3 without uio: <a href="/doc/vmxnet3-usermap">vmxnet3-usermap</a>.
 			</ul>
 		</section>
 	</body>
diff --git a/download.html b/download.html
index 1704053..2a1dedf 100644
--- a/download.html
+++ b/download.html
@@ -41,11 +41,6 @@
 			<p>Latest version: <a href="/browse/dpdk/snapshot/dpdk-2.2.0.tar.gz">2.2.0</a>.</p>
 			<p>Other versions and formats are available from the <a href="/browse/dpdk/refs/">browsing interface</a>.</p>
 			<p>Once downloaded, follow the <a href="/doc/quick-start">quick start instructions</a> to build and run a first test.</p>
-			<h3>Extensions</h3>
-			<ul>
-				<li><a href="/browse/memnic/refs/">memnic</a> &mdash; latest: <a href="/browse/memnic/snapshot/memnic-1.3.tar.gz">1.3</a></li>
-				<li><a href="/browse/vmxnet3-usermap/refs/">vmxnet3-usermap</a> &mdash; latest: <a href="/browse/vmxnet3-usermap/snapshot/vmxnet3-usermap-1.2.tar.gz">1.2</a></li>
-			</ul>
 			<h3>Applications</h3>
 			<ul>
 				<li><a href="/browse/apps/pktgen-dpdk/refs/">pktgen-dpdk (traffic generator)</a></li>
@@ -54,6 +49,11 @@
 			<ul>
 				<li><a href="/browse/tools/dts/refs/">dts (test suite)</a></li>
 			</ul>
+			<h3>Unmaintained Extensions</h3>
+			<ul>
+				<li><a href="/browse/memnic/refs/">memnic</a> &mdash; latest: <a href="/browse/memnic/snapshot/memnic-1.3.tar.gz">1.3</a>
+				<li><a href="/browse/vmxnet3-usermap/refs/">vmxnet3-usermap</a> &mdash; latest: <a href="/browse/vmxnet3-usermap/snapshot/vmxnet3-usermap-1.2.tar.gz">1.2</a>
+			</ul>
 		</section>
 	</body>
 </html>
-- 
2.7.0

             reply	other threads:[~2016-02-12 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 16:41 Thomas Monjalon [this message]
2016-02-18 18:13 ` 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=1455295283-18409-1-git-send-email-thomas.monjalon@6wind.com \
    --to=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).