From: Ankur Dwivedi <adwivedi@marvell.com>
To: <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <david.marchand@redhat.com>,
<ferruh.yigit@amd.com>, <jerinj@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>
Subject: [PATCH v1 5/5] eventdev: remove internal tracepoints from version map
Date: Thu, 9 Feb 2023 19:00:19 +0530 [thread overview]
Message-ID: <20230209133019.933380-6-adwivedi@marvell.com> (raw)
In-Reply-To: <20230209133019.933380-1-adwivedi@marvell.com>
The internal tracepoints are removed from the version.map file.
Signed-off-by: Ankur Dwivedi <adwivedi@marvell.com>
---
lib/eventdev/version.map | 30 ------------------------------
1 file changed, 30 deletions(-)
diff --git a/lib/eventdev/version.map b/lib/eventdev/version.map
index 3add5e3088..9153c09b42 100644
--- a/lib/eventdev/version.map
+++ b/lib/eventdev/version.map
@@ -127,36 +127,6 @@ EXPERIMENTAL {
INTERNAL {
global:
- __rte_eventdev_trace_close;
- __rte_eventdev_trace_configure;
- __rte_eventdev_trace_crypto_adapter_create;
- __rte_eventdev_trace_crypto_adapter_free;
- __rte_eventdev_trace_crypto_adapter_queue_pair_add;
- __rte_eventdev_trace_crypto_adapter_queue_pair_del;
- __rte_eventdev_trace_crypto_adapter_start;
- __rte_eventdev_trace_crypto_adapter_stop;
- __rte_eventdev_trace_eth_rx_adapter_create;
- __rte_eventdev_trace_eth_rx_adapter_free;
- __rte_eventdev_trace_eth_rx_adapter_queue_add;
- __rte_eventdev_trace_eth_rx_adapter_queue_del;
- __rte_eventdev_trace_eth_rx_adapter_start;
- __rte_eventdev_trace_eth_rx_adapter_stop;
- __rte_eventdev_trace_eth_tx_adapter_create;
- __rte_eventdev_trace_eth_tx_adapter_free;
- __rte_eventdev_trace_eth_tx_adapter_queue_add;
- __rte_eventdev_trace_eth_tx_adapter_queue_del;
- __rte_eventdev_trace_eth_tx_adapter_start;
- __rte_eventdev_trace_eth_tx_adapter_stop;
- __rte_eventdev_trace_port_link;
- __rte_eventdev_trace_port_setup;
- __rte_eventdev_trace_port_unlink;
- __rte_eventdev_trace_queue_setup;
- __rte_eventdev_trace_start;
- __rte_eventdev_trace_stop;
- __rte_eventdev_trace_timer_adapter_create;
- __rte_eventdev_trace_timer_adapter_free;
- __rte_eventdev_trace_timer_adapter_start;
- __rte_eventdev_trace_timer_adapter_stop;
event_dev_fp_ops_reset;
event_dev_fp_ops_set;
event_dev_probing_finish;
--
2.25.1
next prev parent reply other threads:[~2023-02-09 13:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 13:30 [PATCH v1 0/5] " Ankur Dwivedi
2023-02-09 13:30 ` [PATCH v1 1/5] mempool: " Ankur Dwivedi
2023-02-09 14:23 ` David Marchand
2023-02-10 5:32 ` [EXT] " Ankur Dwivedi
2023-02-10 5:44 ` Jerin Jacob
2023-02-10 7:00 ` [EXT] " Ankur Dwivedi
2023-02-10 7:06 ` Jerin Jacob
2023-02-10 14:24 ` David Marchand
2023-02-10 15:32 ` Jerin Jacob
2023-02-14 11:37 ` Ankur Dwivedi
2023-02-20 14:18 ` David Marchand
2023-02-09 13:30 ` [PATCH v1 2/5] cryptodev: " Ankur Dwivedi
2023-02-09 13:30 ` [PATCH v1 3/5] eal: " Ankur Dwivedi
2023-02-09 13:30 ` [PATCH v1 4/5] ethdev: " Ankur Dwivedi
2023-02-09 14:13 ` Ferruh Yigit
2023-02-09 13:30 ` Ankur Dwivedi [this message]
2023-02-10 10:34 ` [PATCH v2 0/5] " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 1/5] mempool: " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 2/5] cryptodev: " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 3/5] eal: " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 4/5] ethdev: " Ankur Dwivedi
2023-02-10 14:19 ` David Marchand
2023-02-13 8:14 ` [EXT] " Ankur Dwivedi
2023-02-10 10:34 ` [PATCH v2 5/5] eventdev: " Ankur Dwivedi
2023-02-10 13:08 ` Jerin Jacob
2023-02-15 9:42 ` [PATCH v3 0/5] " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 1/5] mempool: " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 2/5] cryptodev: " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 3/5] eal: " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 4/5] ethdev: " Ankur Dwivedi
2023-02-15 9:42 ` [PATCH v3 5/5] eventdev: " Ankur Dwivedi
2023-02-20 14:39 ` [PATCH v3 0/5] " 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=20230209133019.933380-6-adwivedi@marvell.com \
--to=adwivedi@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jerinj@marvell.com \
--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).