Having different macros for same purpose may cause issues if one is updated without updating the other. Use same macro by including the header.
Signed-off-by: Anoob Joseph <ano...@marvell.com> --- drivers/crypto/cnxk/cnxk_cryptodev.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/crypto/cnxk/cnxk_cryptodev.h b/drivers/crypto/cnxk/cnxk_cryptodev.h index d0ad881f2f..f5374131bf 100644 --- a/drivers/crypto/cnxk/cnxk_cryptodev.h +++ b/drivers/crypto/cnxk/cnxk_cryptodev.h @@ -8,12 +8,12 @@ #include <rte_cryptodev.h> #include <rte_security.h> +#include "roc_ae.h" #include "roc_cpt.h" #define CNXK_CPT_MAX_CAPS 55 #define CNXK_SEC_CRYPTO_MAX_CAPS 16 #define CNXK_SEC_MAX_CAPS 9 -#define CNXK_AE_EC_ID_MAX 9 /** * Device private data */ @@ -23,8 +23,8 @@ struct cnxk_cpt_vf { struct rte_cryptodev_capabilities sec_crypto_caps[CNXK_SEC_CRYPTO_MAX_CAPS]; struct rte_security_capability sec_caps[CNXK_SEC_MAX_CAPS]; - uint64_t cnxk_fpm_iova[CNXK_AE_EC_ID_MAX]; - struct roc_ae_ec_group *ec_grp[CNXK_AE_EC_ID_MAX]; + uint64_t cnxk_fpm_iova[ROC_AE_EC_ID_PMAX]; + struct roc_ae_ec_group *ec_grp[ROC_AE_EC_ID_PMAX]; uint16_t max_qps_limit; }; -- 2.25.1