On 1/9/2018 11:47 AM, De Lara Guarch, Pablo wrote: > > >> -----Original Message----- >> From: dev [mailto:[email protected]] On Behalf Of Tomasz Duszynski >> Sent: Tuesday, January 9, 2018 9:09 AM >> To: [email protected] >> Cc: [email protected]; [email protected]; [email protected]; >> [email protected]; Tomasz Duszynski <[email protected]> >> Subject: [dpdk-dev] [PATCH v3 1/2] crypto/mrvl: sync compilation with >> musdk-17.10 >> >> With a new version of the musdk library it's no longer necessary to >> explicitly define MVCONF_ARCH_DMA_ADDR_T_64BIT. >> >> Proper defines are autogenerated by ./configure script based on passed >> options and available after mv_autogen_comp_flags.h inclusion. >> >> Signed-off-by: Tomasz Duszynski <[email protected]> >> Acked-by: Jianbo Liu <[email protected]> > > Applied to dpdk-next-crypto.
Hi Pablo, Would you be OK if I get this specific patch to the next-net? And merge with net counterpart of it [1]. Because when net and crypto versions are separate patches, one of them is causing build error for a specific version of musdk. When musdk version is updated, both net and crypto should be updated atomically for that new version. [1] https://dpdk.org/dev/patchwork/patch/31927/ > Thanks, > > Pablo >
