DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Radu Nicolau <radu.nicolau@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
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: Mon, 19 Oct 2026 15:16:03 +0100	[thread overview]
Message-ID: <18b34f38-6961-42e1-a828-ca60035a11eb@intel.com> (raw)
In-Reply-To: <8OA9ksWHSu-USgHcEeFFXg@monjalon.net>


On 19-Oct-26 12:27 PM, Thomas Monjalon wrote:
> 19/10/2026 11:25, Radu Nicolau:
>> On 13-Oct-26 8:41 PM, Thomas Monjalon wrote:
>>> 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.
>> Hi Thomas, with the latest changes and removal of minimum required
>> version these patches are now compiling on Arm, are we ok to withdraw
>> the NACK?
> If they compile, yes.
> What changed?

The main change is that they are now rebased on main, and not 
next-crypto, which included the change for IPsec MB min version 2.0.

They compile (and there should be no further issue with Arm compilation)


  reply	other threads:[~2026-10-19 14:16 UTC|newest]

Thread overview: 15+ 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 ` [PATCH v3 0/4] crypto/ipsec_mb: add support for IPsecMB 3.0 Thomas Monjalon
2026-10-19  9:25   ` Radu Nicolau
2026-10-19 11:27     ` Thomas Monjalon
2026-10-19 14:16       ` Radu Nicolau [this message]
2026-10-19 15:04         ` Thomas Monjalon
2026-10-19 15:53           ` Radu Nicolau

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=18b34f38-6961-42e1-a828-ca60035a11eb@intel.com \
    --to=radu.nicolau@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.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