From: Vamsi Attunuru <vattunuru@marvell.com>
To: <dev@dpdk.org>
Cc: <jerinj@marvell.com>, <vattunuru@marvell.com>,
<gakhil@marvell.com>, <ferruh.yigit@intel.com>,
<thomas@monjalon.net>, <mdr@ashroe.eu>
Subject: [PATCH 1/1] doc: notice to add new ipsec event subtypes
Date: Fri, 24 Jun 2022 19:05:51 +0530 [thread overview]
Message-ID: <20220624133551.365962-1-vattunuru@marvell.com> (raw)
Based on discussion in below email thread, the new event subtypes can be
added in 22.11 release with fixing any compatability issues mentioned in
the mail thread.
https://patches.dpdk.org/project/dpdk/patch/20220416192530.173895-8-gakhil@marvell.com/
Signed-off-by: Vamsi Attunuru <vattunuru@marvell.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 4e5b23c53d..83da1c62ac 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -107,6 +107,11 @@ Deprecation Notices
alternative is implemented.
The legacy actions should be removed in DPDK 22.11.
+* ethdev: The enum ``rte_eth_event_ipsec_subtype`` would be extended to add
+ new subtype values ``RTE_ETH_EVENT_IPSEC_SA_PKT_EXPIRY``,
+ ``RTE_ETH_EVENT_IPSEC_SA_BYTE_HARD_EXPIRY`` and
+ ``RTE_ETH_EVENT_IPSEC_SA_PKT_HARD_EXPIRY`` in DPDK 22.11.
+
* cryptodev: Hide structures ``rte_cryptodev_sym_session`` and
``rte_cryptodev_asym_session`` to remove unnecessary indirection between
session and the private data of session. An opaque pointer can be exposed
--
2.25.1
next reply other threads:[~2022-06-24 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 13:35 Vamsi Attunuru [this message]
2022-06-24 18:18 ` Akhil Goyal
2022-06-27 5:29 ` [PATCH v2 1/1] doc: announce addition of " Vamsi Attunuru
2022-07-06 9:49 ` Zhang, Roy Fan
2022-07-11 14:53 ` Jerin Jacob
2022-07-12 11:44 ` Andrew Rybchenko
2022-07-17 10:07 ` Thomas Monjalon
2022-07-12 15:03 ` Thomas Monjalon
2022-07-12 15:30 ` [EXT] " Akhil Goyal
2022-07-12 20:44 ` 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=20220624133551.365962-1-vattunuru@marvell.com \
--to=vattunuru@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=mdr@ashroe.eu \
--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).