19/10/2026 16:16, Radu Nicolau: > > 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 <[email protected]> > >>>> > >>>> 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)
So let's say I remove my NACK. But I am not supportive of the way it is ignoring the Arm fork. I really would like to see a unified repo for IPsec MB.
