From: Anoob Joseph <anoobj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Akhil Goyal <gakhil@marvell.com>,
Jerin Jacob <jerinj@marvell.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>, <dev@dpdk.org>
Subject: [PATCH 2/2] doc: update security guide
Date: Fri, 18 Aug 2023 14:59:43 +0530 [thread overview]
Message-ID: <20230818092943.1771-2-anoobj@marvell.com> (raw)
In-Reply-To: <20230818092943.1771-1-anoobj@marvell.com>
Security library has definitions for configuration parameters of DOCSIS
and MACsec. Remove obsolete comments.
Signed-off-by: Anoob Joseph <anoobj@marvell.com>
---
doc/guides/prog_guide/rte_security.rst | 4 ----
1 file changed, 4 deletions(-)
diff --git a/doc/guides/prog_guide/rte_security.rst b/doc/guides/prog_guide/rte_security.rst
index ae8b0aaef3..b4db4a7bfd 100644
--- a/doc/guides/prog_guide/rte_security.rst
+++ b/doc/guides/prog_guide/rte_security.rst
@@ -693,10 +693,6 @@ The ``rte_security_session_protocol`` is defined as
:start-after: Enumeration of rte_security_session_protocol 8<
:end-before: >8 End enumeration of rte_security_session_protocol.
-Currently the library defines configuration parameters for IPsec and PDCP only.
-For other protocols like MACSec, structures and enums are defined as place holders
-which will be updated in the future.
-
IPsec related configuration parameters are defined in ``rte_security_ipsec_xform``
MACsec related configuration parameters are defined in ``rte_security_macsec_xform``
--
2.25.1
next prev parent reply other threads:[~2023-08-18 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 9:29 [PATCH 1/2] doc: fix code blocks in security guide Anoob Joseph
2023-08-18 9:29 ` Anoob Joseph [this message]
2023-09-19 8:43 ` [PATCH 2/2] doc: update " Akhil Goyal
2023-09-19 8:43 ` [PATCH 1/2] doc: fix code blocks in " 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=20230818092943.1771-2-anoobj@marvell.com \
--to=anoobj@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.