From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: luca.boccassi@gmail.com
Cc: stable@dpdk.org, david.marchand@redhat.com,
Luca Boccassi <bluca@debian.org>
Subject: Re: [PATCH 20.11 v2] cryptodev: add backward-compatible enum
Date: Thu, 17 Mar 2022 18:02:03 +0100 [thread overview]
Message-ID: <CAATJJ0+1PTAZouX-usNPtf-jPy_oRngowMEshtT4oyG_fPSrbA@mail.gmail.com> (raw)
In-Reply-To: <20220317140658.945624-1-luca.boccassi@gmail.com>
On Thu, Mar 17, 2022 at 3:07 PM <luca.boccassi@gmail.com> wrote:
>
> From: Luca Boccassi <bluca@debian.org>
>
> The enum was renamed to fix a typo in main, and backported.
> But in the stable release we want to keep backward compatibility
> when possible, so also define the old name so that both old and
> new code will work.
>
> Fixes: 7b5609a5a0e7 ("cryptodev: fix RSA key type name")
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>
> ---
> Fixed order of comments for doxygen
>
> lib/librte_cryptodev/rte_crypto_asym.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/lib/librte_cryptodev/rte_crypto_asym.h b/lib/librte_cryptodev/rte_crypto_asym.h
> index 9c5bb9233a..d59e05323e 100644
> --- a/lib/librte_cryptodev/rte_crypto_asym.h
> +++ b/lib/librte_cryptodev/rte_crypto_asym.h
> @@ -150,6 +150,8 @@ enum rte_crypto_rsa_priv_key_type {
> /**< RSA private key is in quintuple format
> * See rte_crypto_rsa_priv_key_qt
> */
> + RTE_RSA_KET_TYPE_QT = RTE_RSA_KEY_TYPE_QT,
> + /**< Backward-compatible definition of old name */
I've already applied this merging Lucas first version with David's
feedback and tested it on 19.11.12 and it works fine for me.
Worked on a cross distro/arch build test as well as in the ABI check
(thanks for sharing that BTW).
Tested-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> };
>
> /**
> --
> 2.34.1
>
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
prev parent reply other threads:[~2022-03-17 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 12:23 [PATCH] " luca.boccassi
2022-03-17 13:15 ` David Marchand
2022-03-17 14:06 ` [PATCH 20.11 v2] " luca.boccassi
2022-03-17 17:02 ` Christian Ehrhardt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAATJJ0+1PTAZouX-usNPtf-jPy_oRngowMEshtT4oyG_fPSrbA@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=luca.boccassi@gmail.com \
--cc=stable@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).