From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com, Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [PATCH] doc: announce driver name changes
Date: Sat, 9 Jul 2016 17:56:34 +0100 [thread overview]
Message-ID: <1468083394-94907-1-git-send-email-pablo.de.lara.guarch@intel.com> (raw)
Driver names for all the supported devices in DPDK do not have
a naming convention. Some are using a prefix, some are not
and some have long names. Driver names are used when creating
virtual devices, so it is useful to have consistency in the names.
Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
doc/guides/rel_notes/deprecation.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index f502f86..37d65c8 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -41,3 +41,8 @@ Deprecation Notices
* The mempool functions for single/multi producer/consumer are deprecated and
will be removed in 16.11.
It is replaced by rte_mempool_generic_get/put functions.
+
+* Driver names are quite inconsistent among each others and they will be
+ renamed to something more consistent (net_ prefix for net drivers and
+ crypto_ for crypto drivers) in 16.11. Some of these driver names are used
+ publicly, to create virtual devices, so a deprecation notice is necessary.
--
2.7.4
next reply other threads:[~2016-07-09 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 16:56 Pablo de Lara [this message]
2016-07-11 5:08 ` [PATCH] doc: announce driver name changes Christian Ehrhardt
2016-07-22 12:37 ` De Lara Guarch, Pablo
2016-07-22 12:54 ` Adrien Mazarguil
2016-07-22 13:18 ` Ferruh Yigit
2016-07-22 14:15 ` De Lara Guarch, Pablo
2016-07-22 14:20 ` Thomas Monjalon
2016-07-22 15:13 ` Adrien Mazarguil
2016-07-27 8:30 ` Thomas Monjalon
2016-07-28 17:22 ` Maxime Coquelin
2016-07-28 17:47 ` Jerin Jacob
2016-07-28 17:54 ` 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=1468083394-94907-1-git-send-email-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
/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).