From: Andre Muezerie <andremue@linux.microsoft.com>
To: andremue@linux.microsoft.com
Cc: dev@dpdk.org, fanzhang.oss@gmail.com, gakhil@marvell.com,
mb@smartsharesystems.com
Subject: [PATCH v3 3/3] drivers/crypto: use RTE_BIT64 in initializations of hash_algos
Date: Mon, 27 Jan 2025 11:33:09 -0800 [thread overview]
Message-ID: <1738006389-17193-3-git-send-email-andremue@linux.microsoft.com> (raw)
In-Reply-To: <1738006389-17193-1-git-send-email-andremue@linux.microsoft.com>
This was found during code review of similar issues.
Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
---
drivers/crypto/cnxk/cnxk_cryptodev_capabilities.c | 4 ++--
drivers/crypto/openssl/rte_openssl_pmd_ops.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/crypto/cnxk/cnxk_cryptodev_capabilities.c b/drivers/crypto/cnxk/cnxk_cryptodev_capabilities.c
index 4394513002..e78bc37c37 100644
--- a/drivers/crypto/cnxk/cnxk_cryptodev_capabilities.c
+++ b/drivers/crypto/cnxk/cnxk_cryptodev_capabilities.c
@@ -1207,8 +1207,8 @@ static const struct rte_cryptodev_capabilities caps_eddsa[] = {
{.asym = {
.xform_capa = {
.xform_type = RTE_CRYPTO_ASYM_XFORM_EDDSA,
- .hash_algos = (1 << RTE_CRYPTO_AUTH_SHA512 |
- 1 << RTE_CRYPTO_AUTH_SHAKE_256),
+ .hash_algos = (RTE_BIT64(RTE_CRYPTO_AUTH_SHA512) |
+ RTE_BIT64(RTE_CRYPTO_AUTH_SHAKE_256)),
.op_types = ((1 << RTE_CRYPTO_ASYM_OP_SIGN) |
(1 << RTE_CRYPTO_ASYM_OP_VERIFY))
}
diff --git a/drivers/crypto/openssl/rte_openssl_pmd_ops.c b/drivers/crypto/openssl/rte_openssl_pmd_ops.c
index 18f096abfd..04e018f3df 100644
--- a/drivers/crypto/openssl/rte_openssl_pmd_ops.c
+++ b/drivers/crypto/openssl/rte_openssl_pmd_ops.c
@@ -630,8 +630,8 @@ static const struct rte_cryptodev_capabilities openssl_pmd_capabilities[] = {
{.asym = {
.xform_capa = {
.xform_type = RTE_CRYPTO_ASYM_XFORM_EDDSA,
- .hash_algos = (1 << RTE_CRYPTO_AUTH_SHA512 |
- 1 << RTE_CRYPTO_AUTH_SHAKE_256),
+ .hash_algos = (RTE_BIT64(RTE_CRYPTO_AUTH_SHA512) |
+ RTE_BIT64(RTE_CRYPTO_AUTH_SHAKE_256)),
.op_types =
((1<<RTE_CRYPTO_ASYM_OP_SIGN) |
(1 << RTE_CRYPTO_ASYM_OP_VERIFY)),
--
2.47.2.vfs.0.1
next prev parent reply other threads:[~2025-01-27 19:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 1:53 [PATCH 1/2] lib/cryptodev: avoid implicit conversion to 64 bit number Andre Muezerie
2024-11-28 1:53 ` [PATCH 2/2] lib/hash: " Andre Muezerie
2025-01-22 16:12 ` Bruce Richardson
2025-01-22 21:36 ` Andre Muezerie
2025-01-23 7:55 ` Morten Brørup
2025-01-23 17:42 ` Andre Muezerie
2025-01-25 12:56 ` Morten Brørup
2025-01-22 16:15 ` Medvedkin, Vladimir
2025-01-08 10:28 ` [EXTERNAL] [PATCH 1/2] lib/cryptodev: " Akhil Goyal
2025-01-27 16:03 ` [PATCH v2 " Andre Muezerie
2025-01-27 16:03 ` [PATCH v2 2/2] lib/hash: " Andre Muezerie
2025-01-27 17:16 ` Morten Brørup
2025-01-27 17:14 ` [PATCH v2 1/2] lib/cryptodev: " Morten Brørup
2025-01-27 19:36 ` Andre Muezerie
2025-01-27 19:33 ` [PATCH v3 1/3] " Andre Muezerie
2025-01-27 19:33 ` [PATCH v3 2/3] lib/hash: " Andre Muezerie
2025-01-27 19:33 ` Andre Muezerie [this message]
2025-01-28 7:45 ` [PATCH v3 3/3] drivers/crypto: use RTE_BIT64 in initializations of hash_algos Morten Brørup
2025-01-28 7:49 ` Anoob Joseph
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=1738006389-17193-3-git-send-email-andremue@linux.microsoft.com \
--to=andremue@linux.microsoft.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=mb@smartsharesystems.com \
/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).