20/10/2021 10:31, Akhil Goyal: > > > > Acked-by: Akhil Goyal <gak...@marvell.com> > > > > Patches are rebased over TOT of next-crypto > > > > Release notes are updated > > > > Applied to dpdk-next-crypto > > > > > > I think compilation has not been tested. > > > > I am not sure why this is failing at your end, > > On my machine, it is getting compiled with intel-ipsec-mb v1.0. > > I am double checking compilation for all the individual patches as well. > > Will inform you once it is completed. > > On TOT of next crypto, I did a quick test touched the pmd_zuc.c and it is > > getting compiled. > > cavium@cavium-DT13:~/up/dpdk-next-crypto$ touch > > drivers/crypto/ipsec_mb/pmd_zuc.c > > cavium@cavium-DT13:~/up/dpdk-next-crypto$ ./devtools/test-meson- > > builds.sh > > ninja: Entering directory `./build-gcc-static' > > [24/24] Linking target app/test/dpdk-test. > > ninja: Entering directory `./build-gcc-shared' > > [8/8] Linking target drivers/librte_crypto_ipsec_mb.so.22.0. > > ninja: Entering directory `./build-clang-static' > > [24/24] Linking target app/test/dpdk-test. > > ninja: Entering directory `./build-clang-shared' > > [8/8] Linking target drivers/librte_crypto_ipsec_mb.so.22.0. > > ninja: Entering directory `./build-x86-generic' > > [9/9] Linking target buildtools/chkincs/chkincs. > > ninja: Entering directory `./build-x86-mingw' > > ninja: no work to do. > > > > > You need to update intel-ipsec-mb to v1.0. > I have tried compilation of individual patches as well. It works fine for me. > I see that the ipsec_mb is not in content skipped. So my intel-ipsec-mb > version is 1.0.
It may be due to the fact that I play with CFLAGS and don't install the lib. I will check again for next pull.
