From: Akhil Goyal <gakhil@marvell.com>
To: <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <david.marchand@redhat.com>,
<jerinj@marvell.com>, <anoobj@marvell.com>,
<ndabilpuram@marvell.com>, <pablo.de.lara.guarch@intel.com>,
<hemant.agrawal@nxp.com>, <g.singh@nxp.com>,
<konstantin.v.ananyev@yandex.ru>, <radu.nicolau@intel.com>,
<ciara.power@intel.com>, <ruifeng.wang@arm.com>,
<matan@nvidia.com>, <fanzhang.oss@gmail.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: [PATCH] doc: announce deprecation for security ops
Date: Wed, 5 Jul 2023 01:14:45 +0530 [thread overview]
Message-ID: <20230704194445.3332847-1-gakhil@marvell.com> (raw)
Structure rte_security_ops and rte_security_ctx are meant to
be used by rte_security library and the PMDs associated.
These will be moved to an internal header in DPDK 23.11 release.
Signed-off-by: Akhil Goyal <gakhil@marvell.com>
---
doc/guides/rel_notes/deprecation.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 8e1cdd677a..74bdb4f577 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -133,6 +133,9 @@ Deprecation Notices
``rte_cryptodev_get_auth_algo_string``, ``rte_cryptodev_get_aead_algo_string`` and
``rte_cryptodev_asym_get_xform_string`` respectively.
+* security: Hide structures ``rte_security_ops`` and ``rte_security_ctx`` as these
+ are internal to DPDK library and PMDs.
+
* flow_classify: The flow_classify library and example have no maintainer.
The library is experimental and, as such, it could be removed from DPDK.
Its removal has been postponed to let potential users report interest
--
2.25.1
next reply other threads:[~2023-07-04 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 19:44 Akhil Goyal [this message]
2023-07-05 10:59 ` Hemant Agrawal
2023-07-05 11:31 ` Konstantin Ananyev
2023-07-05 14:06 ` Jerin Jacob
2023-07-06 10:53 ` Power, Ciara
2023-07-06 18:32 ` Akhil Goyal
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=20230704194445.3332847-1-gakhil@marvell.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=ciara.power@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=matan@nvidia.com \
--cc=ndabilpuram@marvell.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
/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).