From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: web@dpdk.org
Subject: [dpdk-web] [PATCH] release 2.2.0
Date: Tue, 15 Dec 2015 17:21:28 +0100 [thread overview]
Message-ID: <1450196488-25199-1-git-send-email-thomas.monjalon@6wind.com> (raw)
---
doc/archives.html | 5 +++++
doc/nics.html | 17 +++++++++++++----
download.html | 2 +-
3 files changed, 19 insertions(+), 5 deletions(-)
diff --git a/doc/archives.html b/doc/archives.html
index b327c82..e409d35 100644
--- a/doc/archives.html
+++ b/doc/archives.html
@@ -38,6 +38,11 @@
</header>
<section>
<h2>Documentation Archives</h2>
+ <p>DPDK 2.2 |
+ <a href="/doc/api-2.2/">HTML API</a> |
+ <a href="/doc/guides-2.2/">HTML guides</a> |
+ <a href="/doc/archives/dpdk-2.2/pdf/guides/">PDF guides</a>
+ </p>
<p>DPDK 2.1 |
<a href="/doc/api-2.1/">HTML API</a> |
<a href="/doc/guides-2.1/">HTML guides</a> |
diff --git a/doc/nics.html b/doc/nics.html
index abab225..a5c601e 100644
--- a/doc/nics.html
+++ b/doc/nics.html
@@ -42,6 +42,10 @@
<ul>
<li><a href="/doc/guides/nics/cxgbe.html">cxgbe</a> (Terminator 5)</li>
</ul>
+ <h3>Cesnet</h3>
+ <ul>
+ <li><a href="/doc/guides/nics/szedata2.html">szedata2</a> (COMBO-80G, COMBO-100G)</li>
+ </ul>
<h3>Cisco</h3>
<ul>
<li><a href="/browse/dpdk/tree/drivers/net/enic">enic</a> (UCS Virtual Interface Card)</li>
@@ -56,18 +60,23 @@
<li><a href="/browse/dpdk/tree/drivers/net/e1000/">e1000e</a> (82571..82574, 82583, ICH8..ICH10, PCH..PCH2)</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, X540, X550)</li>
- <li><a href="/browse/dpdk/tree/drivers/net/i40e/">i40e</a> (X710, XL710)</li>
- <li><a href="/browse/dpdk/tree/drivers/net/fm10k/">fm10k</a></li>
+ <li><a href="/browse/dpdk/tree/drivers/net/i40e/">i40e</a> (X710, XL710, X722)</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>.
The drivers <em>em</em> and <em>igb</em> are sometimes grouped in <em>e1000</em> family.</p>
<h3>Mellanox</h3>
<ul>
<li><a href="/doc/guides/nics/mlx4.html">mlx4</a> (ConnectX-3, ConnectX-3 Pro)</li>
+ <li><a href="/doc/guides/nics/mlx5.html">mlx5</a> (ConnectX-4, ConnectX-4 Lx)</li>
+ </ul>
+ <h3>Netronome</h3>
+ <ul>
+ <li><a href="/doc/guides/nics/nfp.html">nfp</a> (NFP-6xxx)</li>
</ul>
- <h3>QLogic/Broadcom</h3>
+ <h3>QLogic</h3>
<ul>
- <li><a href="/browse/dpdk/tree/drivers/net/bnx2x">bnx2x</a> (NetXtreme II)</li>
+ <li><a href="/doc/guides/nics/bnx2x.html">bnx2x</a> (QLogic 578xx)</li>
</ul>
<h3>Paravirtualization</h3>
<ul>
diff --git a/download.html b/download.html
index 28e5baf..1704053 100644
--- a/download.html
+++ b/download.html
@@ -38,7 +38,7 @@
</header>
<section>
<h2>Download</h2>
- <p>Latest version: <a href="/browse/dpdk/snapshot/dpdk-2.1.0.tar.gz">2.1.0</a>.</p>
+ <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>
--
2.5.2
reply other threads:[~2015-12-15 16:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1450196488-25199-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).