patches for DPDK stable branches
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: stable@dpdk.org
Cc: david.marchand@redhat.com, ktraynor@redhat.com,
	christian.ehrhardt@canonical.com,
	Luca Boccassi <bluca@debian.org>
Subject: [PATCH] cryptodev: add backward-compatible enum
Date: Wed, 16 Mar 2022 12:23:18 +0000	[thread overview]
Message-ID: <20220316122318.718039-1-luca.boccassi@gmail.com> (raw)

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
 	 */
-- 
2.34.1


             reply	other threads:[~2022-03-16 12:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 12:23 luca.boccassi [this message]
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

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=20220316122318.718039-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.com \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=david.marchand@redhat.com \
    --cc=ktraynor@redhat.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).