From: Wathsala Vithanage <wathsala.vithanage@arm.com>
To: Kai Ji <kai.ji@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: gakhil@marvell.com, ciara.power@intel.com, probb@iol.unh.edu,
dev@dpdk.org, nd@arm.com,
Wathsala Vithanage <wathsala.vithanage@arm.com>,
Ruifeng Wang <ruifeng.wang@arm.com>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
Jack Bond-Preston <Jack.Bond-Preston@arm.com>
Subject: [PATCH] crypto/ipsec_mb: update Arm IPsec-MB library tag
Date: Wed, 28 Feb 2024 17:52:50 +0000 [thread overview]
Message-ID: <20240228175250.340922-1-wathsala.vithanage@arm.com> (raw)
Updates the tag of Arm IPsec-MB library to SECLIB-IPSEC-2023.10.13
in snow3g and zuc documentation. Tag SECLIB-IPSEC-2023.10.13 updates
IPSec-MB library version to 1.4.
Signed-off-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Reviewed-by: Jack Bond-Preston <Jack.Bond-Preston@arm.com>
---
doc/guides/cryptodevs/snow3g.rst | 2 +-
doc/guides/cryptodevs/zuc.rst | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/cryptodevs/snow3g.rst b/doc/guides/cryptodevs/snow3g.rst
index 3392932653..e255b1c2c7 100644
--- a/doc/guides/cryptodevs/snow3g.rst
+++ b/doc/guides/cryptodevs/snow3g.rst
@@ -54,7 +54,7 @@ can be downloaded from `<https://github.com/01org/intel-ipsec-mb/archive/v1.5.zi
For Arm system, ARM64 port of the multi-buffer library can be downloaded from
`<https://gitlab.arm.com/arm-reference-solutions/ipsec-mb/-/tree/main/>`_. The
-latest version of the library supported by this PMD is tagged as SECLIB-IPSEC-2023.06.20.
+latest version of the library supported by this PMD is tagged as SECLIB-IPSEC-2023.10.13.
After downloading the library, the user needs to unpack and compile it
on their system before building DPDK:
diff --git a/doc/guides/cryptodevs/zuc.rst b/doc/guides/cryptodevs/zuc.rst
index a414b5ad2c..24454b23a5 100644
--- a/doc/guides/cryptodevs/zuc.rst
+++ b/doc/guides/cryptodevs/zuc.rst
@@ -53,7 +53,7 @@ can be downloaded from `<https://github.com/01org/intel-ipsec-mb/archive/v1.5.zi
For Arm system, ARM64 port of the multi-buffer library can be downloaded from
`<https://gitlab.arm.com/arm-reference-solutions/ipsec-mb/-/tree/main/>`_. The
-latest version of the library supported by this PMD is tagged as SECLIB-IPSEC-2023.06.20.
+latest version of the library supported by this PMD is tagged as SECLIB-IPSEC-2023.10.13.
After downloading the library, the user needs to unpack and compile it
on their system before building DPDK:
--
2.25.1
next reply other threads:[~2024-02-28 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 17:52 Wathsala Vithanage [this message]
2024-03-01 8:15 ` [EXTERNAL] " Akhil Goyal
2024-03-05 16:06 ` Akhil Goyal
2024-03-05 17:44 ` Wathsala Wathawana Vithanage
2024-03-06 14:49 ` [PATCH V2] doc/ipsec_mb: " Wathsala Vithanage
2024-03-12 17:33 ` [PATCH v3] " Jack Bond-Preston
2024-03-14 18:50 ` [EXTERNAL] " Akhil Goyal
2024-03-14 19:54 ` Patrick Robb
2024-03-14 20:04 ` Akhil Goyal
2024-03-15 18:17 ` Patrick Robb
2024-03-22 19:38 ` 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=20240228175250.340922-1-wathsala.vithanage@arm.com \
--to=wathsala.vithanage@arm.com \
--cc=Jack.Bond-Preston@arm.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=kai.ji@intel.com \
--cc=nd@arm.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=probb@iol.unh.edu \
--cc=ruifeng.wang@arm.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).