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>,
	Shepard Siegel <shepard.siegel@atomicrules.com>,
	Ed Czeck <ed.czeck@atomicrules.com>
Subject: [dpdk-web] [PATCH 1/3] move ark pmd back to 17.05
Date: Thu,  6 Apr 2017 15:35:37 +0100	[thread overview]
Message-ID: <20170406143539.16391-1-ferruh.yigit@intel.com> (raw)

Plan is to include ark pmd in 17.05 rc2
http://dpdk.org/ml/archives/dev/2017-March/062713.html

Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
CC: Shepard Siegel <shepard.siegel@atomicrules.com>
CC: Ed Czeck <ed.czeck@atomicrules.com>
---
 dev/roadmap.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index 39af55d..81ed290 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -58,12 +58,12 @@
 		<li>Automated VF processing of PF Reset for i40e
 		<li>Consistent PMD Batching behaviour
 		<li>Cryptodev DOCSIS BPI+
+		<li>Atomic Rules Arkville Driver
 	</ul>
 	<h3 id="1708">Version 17.08 (2017 August)</h3>
 	<ul>
 		<li>Hotplug Notification
 		<li>Automatic Device Binding
-		<li>Atomic Rules Arkville Driver
 		<li>Xen Netfront Driver
 	</ul>
 	<h3 id="cycle">Cycle model</h3>
-- 
2.9.3

             reply	other threads:[~2017-04-06 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 14:35 Ferruh Yigit [this message]
2017-04-06 14:35 ` [dpdk-web] [PATCH 2/3] move bnxt pmd update to 17.08 Ferruh Yigit
2017-04-06 14:35 ` [dpdk-web] [PATCH 3/3] announce enic pmd update for 17.08 Ferruh Yigit
2017-04-06 14:57 ` [dpdk-web] [PATCH 1/3] move ark pmd back to 17.05 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=20170406143539.16391-1-ferruh.yigit@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=ed.czeck@atomicrules.com \
    --cc=shepard.siegel@atomicrules.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).