On 10/9/2024 12:24 PM, Akhil Goyal wrote:
> RTE_CRYPTO_ASYM_XFORM_TYPE_LIST_END and
> RTE_CRYPTO_RSA_PADDING_TYPE_LIST_END are not used anywhere and
> mostly it do not fulfil any objective.
> Rather it does not allow addition of new algorithms and
> new padding type as it result in ABI breakage.
> Hence, these are removed.
>
> Signed-off-by: Akhil Goyal <gak...@marvell.com>
> ---
> lib/cryptodev/rte_crypto_asym.h | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/lib/cryptodev/rte_crypto_asym.h b/lib/cryptodev/rte_crypto_asym.h
> index 39d3da3952..524753e2b2 100644
> --- a/lib/cryptodev/rte_crypto_asym.h
> +++ b/lib/cryptodev/rte_crypto_asym.h
> @@ -119,8 +119,6 @@ enum rte_crypto_asym_xform_type {
> * Performs Encrypt, Decrypt, Sign and Verify.
> * Refer to rte_crypto_asym_op_type.
> */
> - RTE_CRYPTO_ASYM_XFORM_TYPE_LIST_END
> - /**< End of list */
> };
>
> /**
> @@ -168,7 +166,6 @@ enum rte_crypto_rsa_padding_type {
> /**< RSA PKCS#1 OAEP padding scheme */
> RTE_CRYPTO_RSA_PADDING_PSS,
> /**< RSA PKCS#1 PSS padding scheme */
> - RTE_CRYPTO_RSA_PADDING_TYPE_LIST_END
> };
>
> /**
I can see this is already merged, but for record, +1 to this approach.
