[PATCH 1/4] rte_log: take of some experimental tags
Stephen Hemminger
stephen at networkplumber.org
Wed Feb 16 20:39:14 CET 2022
The RTE_LOG_REGISTER is not experimental, and the experimental
tag was never enforced on these.
Make rte_log_can_log a fully supported function.
It was introduced nearly 2yrs ago.
Signed-off-by: Stephen Hemminger <stephen at networkplumber.org>
---
lib/eal/include/rte_log.h | 10 ----------
lib/eal/version.map | 2 +-
2 files changed, 1 insertion(+), 11 deletions(-)
diff --git a/lib/eal/include/rte_log.h b/lib/eal/include/rte_log.h
index 319e4044a5c8..25ce42cdfc4d 100644
--- a/lib/eal/include/rte_log.h
+++ b/lib/eal/include/rte_log.h
@@ -136,7 +136,6 @@ int rte_log_get_level(uint32_t logtype);
* @return
* Returns 'true' if log can be printed and 'false' if it can't.
*/
-__rte_experimental
bool rte_log_can_log(uint32_t logtype, uint32_t loglevel);
/**
@@ -378,9 +377,6 @@ RTE_INIT(__##type) \
}
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
* Register a dynamic log type in constructor context with its name and level.
*
* It is a wrapper macro for declaring the logtype, register the log and
@@ -397,9 +393,6 @@ RTE_INIT(__##type) \
RTE_LOG_REGISTER_IMPL(type, RTE_STR(name), level)
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
* This is an equivalent to RTE_LOG_REGISTER, but relying on the build system
* to select the right format for the logtype.
*/
@@ -407,9 +400,6 @@ RTE_INIT(__##type) \
RTE_LOG_REGISTER_IMPL(type, RTE_STR(RTE_LOG_DEFAULT_LOGTYPE), level)
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice
- *
* This is an equivalent to RTE_LOG_REGISTER, but relying on the build system
* to select the right prefix for the logtype.
*/
diff --git a/lib/eal/version.map b/lib/eal/version.map
index b53eeb30d74f..6b1657d0d8bd 100644
--- a/lib/eal/version.map
+++ b/lib/eal/version.map
@@ -129,6 +129,7 @@ DPDK_22 {
rte_lcore_iterate;
rte_lcore_to_socket_id;
rte_log;
+ rte_log_can_log;
rte_log_cur_msg_loglevel;
rte_log_cur_msg_logtype;
rte_log_dump;
@@ -364,7 +365,6 @@ EXPERIMENTAL {
__rte_trace_point_register;
per_lcore_trace_mem;
per_lcore_trace_point_sz;
- rte_log_can_log;
rte_thread_getname; # WINDOWS_NO_EXPORT
rte_trace_dump; # WINDOWS_NO_EXPORT
rte_trace_is_enabled; # WINDOWS_NO_EXPORT
--
2.34.1
More information about the dev
mailing list