From: Thomas Monjalon <thomas@monjalon.net>
To: Radu Nicolau <radu.nicolau@intel.com>
Cc: dev@dpdk.org, Kai Ji <kai.ji@intel.com>
Subject: Re: [PATCH v3 0/4] crypto/ipsec_mb: add support for IPsecMB 3.0
Date: Tue, 13 Oct 2026 21:41:47 +0200 [thread overview]
Message-ID: <Fb4CjKFWRziKn9hdw7IRLA@monjalon.net> (raw)
In-Reply-To: <20261012135947.1895429-1-radu.nicolau@intel.com>
12/10/2026 15:58, Radu Nicolau:
> Intel(R) Multi-Buffer Crypto for IPsec Library released version 3.0.0
> codenamed Túnel Pablo
> https://github.com/intel/intel-ipsec-mb/releases/tag/v3.0.0
>
> This patchset adds support for the new library version and support
> for the new algorithms included in this release.
>
> Series-acked-by: Kai Ji <kai.ji@intel.com>
>
> Radu Nicolau (4):
> crypto/ipsec_mb: add support for IPsecMB 3.0
> crypto/ipsec_mb: add support for 256-NxA4/5/6 algorithms
> crypto/ipsec_mb: add support for ML-KEM and ML-DSA
> test/crypto: add asym test suite for AESNI_MB
Sorry I will give a defensive NACK
because you never fixed the problem with the Arm fork.
The crypto branch is already not compiling on Arm
because of your recent change for IPsec MB 2.0.
prev parent reply other threads:[~2026-10-13 19:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 13:58 [PATCH v3 0/4] crypto/ipsec_mb: add support for IPsecMB 3.0 Radu Nicolau
2026-10-12 13:58 ` [PATCH v3 1/4] " Radu Nicolau
2026-10-12 15:52 ` Cornu, Marcel D
2026-10-13 9:36 ` Cornu, Marcel D
2026-10-12 13:58 ` [PATCH v3 2/4] crypto/ipsec_mb: add support for 256-NxA4/5/6 algorithms Radu Nicolau
2026-10-13 10:41 ` Cornu, Marcel D
2026-10-12 13:58 ` [PATCH v3 3/4] crypto/ipsec_mb: add support for ML-KEM and ML-DSA Radu Nicolau
2026-10-13 12:48 ` Cornu, Marcel D
2026-10-12 13:58 ` [PATCH v3 4/4] test/crypto: add asym test suite for AESNI_MB Radu Nicolau
2026-10-13 19:41 ` Thomas Monjalon [this message]
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=Fb4CjKFWRziKn9hdw7IRLA@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=radu.nicolau@intel.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