From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Ray Kinsella <mdr@ashroe.eu>
Subject: [PATCH 1/4] rte_log: take of some experimental tags
Date: Wed, 16 Feb 2022 11:39:14 -0800 [thread overview]
Message-ID: <20220216193917.251657-2-stephen@networkplumber.org> (raw)
In-Reply-To: <20220216193917.251657-1-stephen@networkplumber.org>
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@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
next prev parent reply other threads:[~2022-02-16 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 19:39 [PATCH 0/4] eal: remove " Stephen Hemminger
2022-02-16 19:39 ` Stephen Hemminger [this message]
2022-02-17 12:57 ` [PATCH 1/4] rte_log: take of " Ray Kinsella
2022-02-16 19:39 ` [PATCH 2/4] lcore: change rte_lcore_to_cpu_id and rte_lcore_cpuset as not experimental Stephen Hemminger
2022-02-17 12:55 ` Ray Kinsella
2022-02-16 19:39 ` [PATCH 3/4] eal: make some intr functions " Stephen Hemminger
2022-02-17 12:56 ` Ray Kinsella
2022-02-16 19:39 ` [PATCH 4/4] eal: mark rte_delay_us_sleep as " Stephen Hemminger
2022-02-17 12:56 ` Ray Kinsella
2022-06-26 15:34 ` [PATCH 0/4] eal: remove some experimental tags 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=20220216193917.251657-2-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=mdr@ashroe.eu \
/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).