DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH] telemetry: promote experimental API to stable
Date: Wed,  2 Sep 2026 16:26:30 -0700	[thread overview]
Message-ID: <20260902232630.543215-1-stephen@networkplumber.org> (raw)

The remaining experimental telemetry functions have been present without
interface changes for several releases: the hexadecimal helpers
rte_tel_data_add_array_uint_hex() and rte_tel_data_add_dict_uint_hex()
since v23.03, and rte_telemetry_register_cmd_arg() since v24.11.
Promote all three to the stable ABI.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 doc/guides/rel_notes/release_26_11.rst | 6 ++++++
 lib/telemetry/rte_telemetry.h          | 3 ---
 lib/telemetry/telemetry.c              | 2 +-
 lib/telemetry/telemetry_data.c         | 4 ++--
 4 files changed, 9 insertions(+), 6 deletions(-)

diff --git a/doc/guides/rel_notes/release_26_11.rst b/doc/guides/rel_notes/release_26_11.rst
index 87c7e81bde..edca1f445c 100644
--- a/doc/guides/rel_notes/release_26_11.rst
+++ b/doc/guides/rel_notes/release_26_11.rst
@@ -95,6 +95,12 @@ API Changes
    Also, make sure to start the actual text at the margin.
    =======================================================
 
+* telemetry: Promoted the following functions to stable:
+
+  * ``rte_tel_data_add_array_uint_hex``
+  * ``rte_tel_data_add_dict_uint_hex``
+  * ``rte_telemetry_register_cmd_arg``
+
 
 ABI Changes
 -----------
diff --git a/lib/telemetry/rte_telemetry.h b/lib/telemetry/rte_telemetry.h
index 0a58e518f7..f5b2aa1415 100644
--- a/lib/telemetry/rte_telemetry.h
+++ b/lib/telemetry/rte_telemetry.h
@@ -174,7 +174,6 @@ rte_tel_data_add_array_container(struct rte_tel_data *d,
  * @return
  *   0 on success, negative errno on error.
  */
-__rte_experimental
 int
 rte_tel_data_add_array_uint_hex(struct rte_tel_data *d, uint64_t val,
 		uint8_t display_bitwidth);
@@ -276,7 +275,6 @@ rte_tel_data_add_dict_container(struct rte_tel_data *d, const char *name,
  * @return
  *   0 on success, negative errno on error.
  */
-__rte_experimental
 int
 rte_tel_data_add_dict_uint_hex(struct rte_tel_data *d, const char *name,
 		uint64_t val, uint8_t display_bitwidth);
@@ -364,7 +362,6 @@ rte_telemetry_register_cmd(const char *cmd, telemetry_cb fn, const char *help);
  * @return
  *   -ENOMEM for mem allocation failure.
  */
-__rte_experimental
 int
 rte_telemetry_register_cmd_arg(const char *cmd, telemetry_arg_cb fn, void *arg, const char *help);
 
diff --git a/lib/telemetry/telemetry.c b/lib/telemetry/telemetry.c
index e591c1e283..379dbf4ce3 100644
--- a/lib/telemetry/telemetry.c
+++ b/lib/telemetry/telemetry.c
@@ -122,7 +122,7 @@ rte_telemetry_register_cmd(const char *cmd, telemetry_cb fn, const char *help)
 	return register_cmd(cmd, help, fn, NULL, NULL);
 }
 
-RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_telemetry_register_cmd_arg, 24.11)
+RTE_EXPORT_SYMBOL(rte_telemetry_register_cmd_arg)
 int
 rte_telemetry_register_cmd_arg(const char *cmd, telemetry_arg_cb fn, void *arg, const char *help)
 {
diff --git a/lib/telemetry/telemetry_data.c b/lib/telemetry/telemetry_data.c
index 0a006559ab..8e0f4c515b 100644
--- a/lib/telemetry/telemetry_data.c
+++ b/lib/telemetry/telemetry_data.c
@@ -124,7 +124,7 @@ rte_tel_uint_to_hex_encoded_str(char *buf, size_t buf_len, uint64_t val,
 	return len < (int)buf_len ? 0 : -EINVAL;
 }
 
-RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_tel_data_add_array_uint_hex, 23.03)
+RTE_EXPORT_SYMBOL(rte_tel_data_add_array_uint_hex)
 int
 rte_tel_data_add_array_uint_hex(struct rte_tel_data *d, uint64_t val,
 				uint8_t display_bitwidth)
@@ -248,7 +248,7 @@ rte_tel_data_add_dict_container(struct rte_tel_data *d, const char *name,
 	return bytes < RTE_TEL_MAX_STRING_LEN ? 0 : E2BIG;
 }
 
-RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_tel_data_add_dict_uint_hex, 23.03)
+RTE_EXPORT_SYMBOL(rte_tel_data_add_dict_uint_hex)
 int
 rte_tel_data_add_dict_uint_hex(struct rte_tel_data *d, const char *name,
 			       uint64_t val, uint8_t display_bitwidth)
-- 
2.53.0


             reply	other threads:[~2026-09-02 23:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 23:26 Stephen Hemminger [this message]
2026-09-03  8:19 ` [PATCH] telemetry: promote experimental API to stable Bruce Richardson

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=20260902232630.543215-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=bruce.richardson@intel.com \
    --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