From: okaya@kernel.org
Cc: dev@dpdk.org, Sinan Kaya <okaya@kernel.org>
Subject: [PATCH v5 10/10] test: remove double registration check
Date: Thu, 17 Aug 2023 00:30:27 -0400 [thread overview]
Message-ID: <20230817043027.138473-1-okaya@kernel.org> (raw)
From: Sinan Kaya <okaya@kernel.org>
Code will fetch the existing registration when called
for second time as part of the reinit changes.
Registration will still succeed.
Signed-off-by: Sinan Kaya <okaya@kernel.org>
---
app/test/test_tailq.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/app/test/test_tailq.c b/app/test/test_tailq.c
index 9520219b0a..fbb483ea86 100644
--- a/app/test/test_tailq.c
+++ b/app/test/test_tailq.c
@@ -70,11 +70,6 @@ test_tailq_create(void)
if (strcmp(rte_dummy_dyn2_tailq.name, rte_dummy_dyn_tailq.name))
do_return("Error, something is wrong in the tailq test\n");
- /* try allocating again, and check for failure */
- if (!rte_eal_tailq_register(&rte_dummy_dyn2_tailq))
- do_return("Error, registering the same tailq %s did not fail\n",
- rte_dummy_dyn2_tailq.name);
-
return 0;
}
--
2.25.1
reply other threads:[~2023-08-17 4:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230817043027.138473-1-okaya@kernel.org \
--to=okaya@kernel.org \
--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).