From: Rebecca Troy <rebecca.troy@intel.com>
To: dev@dpdk.org
Cc: ciara.power@intel.com, Rebecca Troy <rebecca.troy@intel.com>,
Declan Doherty <declan.doherty@intel.com>
Subject: [dpdk-dev] [PATCH] test/crypto: use formal array size macro
Date: Mon, 5 Jul 2021 11:50:30 +0000 [thread overview]
Message-ID: <20210705115030.520497-1-rebecca.troy@intel.com> (raw)
Replaces the use of local ARRAY_SIZE macro, which is not used
anywhere else, with the formal RTE_DIM macro for better
consistency in crypto unit test.
Signed-off-by: Rebecca Troy <rebecca.troy@intel.com>
---
app/test/test_cryptodev.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
index 39db52b17a..b5ac5b048a 100644
--- a/app/test/test_cryptodev.c
+++ b/app/test/test_cryptodev.c
@@ -61,10 +61,6 @@
#define IN_PLACE 0
#define OUT_OF_PLACE 1
-#ifndef ARRAY_SIZE
-#define ARRAY_SIZE(x) (sizeof(x) / sizeof((x)[0]))
-#endif
-
static int gbl_driver_id;
static enum rte_security_session_action_type gbl_action_type =
@@ -8736,7 +8732,7 @@ test_PDCP_SDAP_PROTO_encap_all(void)
int err, all_err = TEST_SUCCESS;
const struct pdcp_sdap_test *cur_test;
- size = ARRAY_SIZE(list_pdcp_sdap_tests);
+ size = RTE_DIM(list_pdcp_sdap_tests);
for (i = 0; i < size; i++) {
cur_test = &list_pdcp_sdap_tests[i];
@@ -8778,7 +8774,7 @@ test_PDCP_SDAP_PROTO_decap_all(void)
int err, all_err = TEST_SUCCESS;
const struct pdcp_sdap_test *cur_test;
- size = ARRAY_SIZE(list_pdcp_sdap_tests);
+ size = RTE_DIM(list_pdcp_sdap_tests);
for (i = 0; i < size; i++) {
cur_test = &list_pdcp_sdap_tests[i];
--
2.25.1
next reply other threads:[~2021-07-05 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 11:50 Rebecca Troy [this message]
2021-07-06 12:18 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-07 14:40 ` Akhil Goyal
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=20210705115030.520497-1-rebecca.troy@intel.com \
--to=rebecca.troy@intel.com \
--cc=ciara.power@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@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).