DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Subject: [dpdk-web] [PATCH] postpone automatic binding in roadmap
Date: Wed, 17 May 2017 14:06:47 +0200	[thread overview]
Message-ID: <20170517120647.3410-1-thomas@monjalon.net> (raw)

The idea of automatic device binding to kernel modules
is floating around since a long time and it is postponed
from release to release until someone work on it.

It won't be in 17.08 because the priority will be on finishing
the bus rework.

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 dev/roadmap.html | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/dev/roadmap.html b/dev/roadmap.html
index 5c7c8e8..df0ece3 100644
--- a/dev/roadmap.html
+++ b/dev/roadmap.html
@@ -44,7 +44,6 @@
 	<h3 id="1708">Version 17.08 (2017 August)</h3>
 	<ul>
 		<li>Hotplug Notification
-		<li>Automatic Device Binding
 		<li>Xen Netfront Driver
 		<li>Enhance bnxt driver and update the HWRM version
 		<li>Enic flow API support
@@ -59,6 +58,10 @@
 		<li>Generic Receive Offload
 		<li>Cryptodev Multi-Core SW Scheduler
 	</ul>
+	<h3 id="1711">Version 17.11 (2017 November)</h3>
+	<ul>
+		<li>Automatic Device Binding
+	</ul>
 	<h3 id="cycle">Cycle model</h3>
 	<p>A typical release should be done after 3 months.
 	<p>It is designed to allow DPDK to keep evolving at a rapid pace while
-- 
2.13.0

             reply	other threads:[~2017-05-17 12:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 12:06 Thomas Monjalon [this message]
2017-05-30 20:21 ` 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=20170517120647.3410-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --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).