From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: stable@dpdk.org, Matan Azrad <matan@nvidia.com>,
Raja Zidane <rzidane@nvidia.com>,
Tal Shnaiderman <talshn@nvidia.com>,
Shiri Kuzin <shirik@nvidia.com>, Akhil Goyal <gakhil@marvell.com>
Subject: [PATCH 2/5] crypto/mlx5: remove unused constants
Date: Sun, 2 Nov 2025 16:53:01 +0100 [thread overview]
Message-ID: <20251102155617.4001783-3-thomas@monjalon.net> (raw)
In-Reply-To: <20251102155617.4001783-1-thomas@monjalon.net>
The constant MLX5_CRYPTO_LOG_NAME was never used.
The constant MLX5_CRYPTO_MAX_SEGS was not used after the fix below.
Fixes: ba707cdb6da2 ("crypto/mlx5: fix queue size configuration")
Fixes: a7c86884f150 ("crypto/mlx5: introduce Mellanox crypto driver")
Cc: stable@dpdk.org
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
drivers/crypto/mlx5/mlx5_crypto.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/crypto/mlx5/mlx5_crypto.c b/drivers/crypto/mlx5/mlx5_crypto.c
index 78a9e3d0fe..6b36a3ece5 100644
--- a/drivers/crypto/mlx5/mlx5_crypto.c
+++ b/drivers/crypto/mlx5/mlx5_crypto.c
@@ -19,9 +19,7 @@
#include "mlx5_crypto.h"
#define MLX5_CRYPTO_DRIVER_NAME crypto_mlx5
-#define MLX5_CRYPTO_LOG_NAME pmd.crypto.mlx5
#define MLX5_CRYPTO_MAX_QPS 128
-#define MLX5_CRYPTO_MAX_SEGS 56
#define MLX5_CRYPTO_FEATURE_FLAGS(wrapped_mode) \
(RTE_CRYPTODEV_FF_SYMMETRIC_CRYPTO | RTE_CRYPTODEV_FF_HW_ACCELERATED | \
--
2.51.0
next prev parent reply other threads:[~2025-11-02 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251102155617.4001783-1-thomas@monjalon.net>
2025-11-02 15:53 ` [PATCH 1/5] vdpa/mlx5: remove unused constant Thomas Monjalon
2025-11-02 15:53 ` Thomas Monjalon [this message]
2025-11-02 15:53 ` [PATCH 3/5] regex/mlx5: remove useless constants Thomas Monjalon
2025-11-02 15:53 ` [PATCH 4/5] common/mlx5: " Thomas Monjalon
2025-11-02 15:53 ` [PATCH 5/5] net/mlx5: " Thomas Monjalon
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=20251102155617.4001783-3-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=matan@nvidia.com \
--cc=rzidane@nvidia.com \
--cc=shirik@nvidia.com \
--cc=stable@dpdk.org \
--cc=talshn@nvidia.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).