From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: [dpdk-dev] [PATCH] doc: announce deprecation of rawdev exposed array
Date: Thu, 15 Nov 2018 13:08:14 +0000 [thread overview]
Message-ID: <20181115130729.1451-1-shreyansh.jain@nxp.com> (raw)
rte_rawdevs is expected to be deprecated in future releases. This is
not expected to be directly used, without API access that is, by any
external application or driver.
Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
---
This is in sync with discussion in [1]
[1] http://mails.dpdk.org/archives/dev/2018-October/114592.html
---
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 34b28234c..776b9b245 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -55,3 +55,8 @@ Deprecation Notices
- ``rte_pdump_set_socket_dir`` will be removed;
- The parameter, ``path``, of ``rte_pdump_init`` will be removed;
- The enum ``rte_pdump_socktype`` will be removed.
+
+* rawdev: ``rte_rawdevs`` is an array containing all registered raw devices.
+ Currently this is exposed from the library. Ideally, no application should
+ be directly using it. This is expected to be deprecated and made internal
+ in v19.02 or later.
--
2.17.1
next reply other threads:[~2018-11-15 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 13:08 Shreyansh Jain [this message]
2018-11-23 16:32 ` Jerin Jacob
2018-11-24 17:33 ` Thomas Monjalon
2018-11-26 8:35 ` Shreyansh Jain
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=20181115130729.1451-1-shreyansh.jain@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=dev@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).