From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: web@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
Stephen Hurd <stephen.hurd@broadcom.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: [dpdk-web] [PATCH 2/3] move bnxt pmd update to 17.08
Date: Thu, 6 Apr 2017 15:35:38 +0100 [thread overview]
Message-ID: <20170406143539.16391-2-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20170406143539.16391-1-ferruh.yigit@intel.com>
bnxt pmd update sent after propasol deadline and defered to 17.08
http://dpdk.org/ml/archives/dev/2017-March/061620.html
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
CC: Stephen Hurd <stephen.hurd@broadcom.com>
CC: Ajit Khaparde <ajit.khaparde@broadcom.com>
---
dev/roadmap.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev/roadmap.html b/dev/roadmap.html
index 81ed290..81e8502 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -53,7 +53,6 @@
<li>Interrupt Mode for virtio-user
<li>New device types in vhost-user
<li>Add flow API and virtual functions support in the Solarflare net driver
- <li>Enhance bnxt driver and update the HWRM version to 1.7.1
<li>Tunnel and MPLS filters for i40e
<li>Automated VF processing of PF Reset for i40e
<li>Consistent PMD Batching behaviour
@@ -65,6 +64,7 @@
<li>Hotplug Notification
<li>Automatic Device Binding
<li>Xen Netfront Driver
+ <li>Enhance bnxt driver and update the HWRM version
</ul>
<h3 id="cycle">Cycle model</h3>
<p>A typical release should be done after 3 months.
--
2.9.3
next prev parent 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 [dpdk-web] [PATCH 1/3] move ark pmd back to 17.05 Ferruh Yigit
2017-04-06 14:35 ` Ferruh Yigit [this message]
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-2-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=stephen.hurd@broadcom.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).