From: David Marchand <david.marchand@redhat.com>
To: Luca Boccassi <luca.boccassi@gmail.com>
Cc: dpdk stable <stable@dpdk.org>,
Kevin Traynor <ktraynor@redhat.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Luca Boccassi <bluca@debian.org>
Subject: Re: [PATCH] cryptodev: add backward-compatible enum
Date: Thu, 17 Mar 2022 14:15:15 +0100 [thread overview]
Message-ID: <CAJFAV8wTDsOf98w2gW7gfKp_pLwimvrZ-wpXDTLbbw90vuVN6Q@mail.gmail.com> (raw)
In-Reply-To: <20220316122318.718039-1-luca.boccassi@gmail.com>
On Wed, Mar 16, 2022 at 1:23 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>
> ---
> Thanks David for the report. Might be interesting for other LTS branches too.
>
> 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..8133a31ad4 100644
> --- a/lib/librte_cryptodev/rte_crypto_asym.h
> +++ b/lib/librte_cryptodev/rte_crypto_asym.h
> @@ -147,6 +147,8 @@ enum rte_crypto_rsa_priv_key_type {
> RTE_RSA_KEY_TYPE_EXP,
> /**< RSA private key is an exponent */
> RTE_RSA_KEY_TYPE_QT,
> + /**< Backward-compatible definition of old name */
> + RTE_RSA_KET_TYPE_QT = RTE_RSA_KEY_TYPE_QT,
> /**< RSA private key is in quintuple format
> * See rte_crypto_rsa_priv_key_qt
> */
You should move this compat item after the comment.
Idem the doxygen tag should be *after* the new item.
Like:
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 tried this patch (after moving the hunk after the comment) on top of
current 20.11 branch.
It fixes the ABI check (more a API check in this case).
--
David Marchand
next prev parent reply other threads:[~2022-03-17 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 12:23 luca.boccassi
2022-03-17 13:15 ` David Marchand [this message]
2022-03-17 14:06 ` [PATCH 20.11 v2] " luca.boccassi
2022-03-17 17:02 ` Christian Ehrhardt
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=CAJFAV8wTDsOf98w2gW7gfKp_pLwimvrZ-wpXDTLbbw90vuVN6Q@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ktraynor@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).