From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, bruce.richardson@intel.com,
andremue@linux.microsoft.com
Subject: [RFC 09/10] app/compress-perf: remove weak symbols
Date: Fri, 7 Feb 2025 09:32:49 +0100 [thread overview]
Message-ID: <20250207083252.3131588-10-david.marchand@redhat.com> (raw)
In-Reply-To: <20250207083252.3131588-1-david.marchand@redhat.com>
Remove dead code, those symbols are never used as the "strong" symbols
are always linked in.
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
app/test-compress-perf/main.c | 62 -----------------------------------
1 file changed, 62 deletions(-)
diff --git a/app/test-compress-perf/main.c b/app/test-compress-perf/main.c
index fa366123ed..70ce4316cc 100644
--- a/app/test-compress-perf/main.c
+++ b/app/test-compress-perf/main.c
@@ -521,65 +521,3 @@ main(int argc, char **argv)
}
return ret;
}
-
-__rte_weak void *
-cperf_cyclecount_test_constructor(uint8_t dev_id __rte_unused,
- uint16_t qp_id __rte_unused,
- struct comp_test_data *options __rte_unused)
-{
- RTE_LOG(INFO, USER1, "Cycle count test is not supported yet\n");
- return NULL;
-}
-
-__rte_weak void
-cperf_cyclecount_test_destructor(void *arg __rte_unused)
-{
- RTE_LOG(INFO, USER1, "Something wrong happened!!!\n");
-}
-
-__rte_weak int
-cperf_cyclecount_test_runner(void *test_ctx __rte_unused)
-{
- return 0;
-}
-
-__rte_weak void *
-cperf_throughput_test_constructor(uint8_t dev_id __rte_unused,
- uint16_t qp_id __rte_unused,
- struct comp_test_data *options __rte_unused)
-{
- RTE_LOG(INFO, USER1, "Benchmark test is not supported yet\n");
- return NULL;
-}
-
-__rte_weak void
-cperf_throughput_test_destructor(void *arg __rte_unused)
-{
-
-}
-
-__rte_weak int
-cperf_throughput_test_runner(void *test_ctx __rte_unused)
-{
- return 0;
-}
-__rte_weak void *
-cperf_verify_test_constructor(uint8_t dev_id __rte_unused,
- uint16_t qp_id __rte_unused,
- struct comp_test_data *options __rte_unused)
-{
- RTE_LOG(INFO, USER1, "Verify test is not supported yet\n");
- return NULL;
-}
-
-__rte_weak void
-cperf_verify_test_destructor(void *arg __rte_unused)
-{
-
-}
-
-__rte_weak int
-cperf_verify_test_runner(void *test_ctx __rte_unused)
-{
- return 0;
-}
--
2.48.1
next prev parent reply other threads:[~2025-02-07 8:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 8:32 [RFC 00/10] Remove " David Marchand
2025-02-07 8:32 ` [RFC 01/10] bus/auxiliary: remove " David Marchand
2025-02-07 8:32 ` [RFC 02/10] common/qat: " David Marchand
2025-02-07 8:32 ` [RFC 03/10] drivers: remove weak symbols in Nitrox drivers David Marchand
2025-02-07 8:32 ` [RFC 04/10] net/enic: remove weak symbols David Marchand
2025-02-07 8:32 ` [RFC 05/10] net/hns3: " David Marchand
2025-02-07 8:32 ` [RFC 06/10] net/fm10k: " David Marchand
2025-02-07 8:51 ` Bruce Richardson
2025-02-07 8:32 ` [RFC 07/10] net/nfp: " David Marchand
2025-02-07 8:44 ` Chaoyong He
2025-02-07 8:32 ` [RFC 08/10] net/virtio: " David Marchand
2025-02-07 8:32 ` David Marchand [this message]
2025-02-07 8:32 ` [RFC 10/10] eal: deprecate " David Marchand
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=20250207083252.3131588-10-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=andremue@linux.microsoft.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).