From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org
Cc: Olivier Matz <olivier.matz@6wind.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Xueming Li <xuemingl@nvidia.com>, Gaetan Rivet <grive@u256.net>,
Ray Kinsella <mdr@ashroe.eu>
Subject: [dpdk-dev] [PATCH v2 1/5] kvargs: promote delimited parsing as stable
Date: Wed, 29 Sep 2021 23:39:39 +0200 [thread overview]
Message-ID: <20210929213943.17817-2-olivier.matz@6wind.com> (raw)
In-Reply-To: <20210929213943.17817-1-olivier.matz@6wind.com>
This function is used by EAL to parse key/value strings separated with
specified delimiters.
It was introduced in 2018 by commit 5d6af85ab00c ("kvargs: introduce a
more flexible parsing function"), and can be promoted as stable.
Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
Reviewed-by: Xueming Li <xuemingl@nvidia.com>
---
lib/kvargs/rte_kvargs.h | 1 -
lib/kvargs/version.map | 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/lib/kvargs/rte_kvargs.h b/lib/kvargs/rte_kvargs.h
index 12a8f90435..c30891c668 100644
--- a/lib/kvargs/rte_kvargs.h
+++ b/lib/kvargs/rte_kvargs.h
@@ -98,7 +98,6 @@ struct rte_kvargs *rte_kvargs_parse(const char *args,
* - A pointer to an allocated rte_kvargs structure on success
* - NULL on error
*/
-__rte_experimental
struct rte_kvargs *rte_kvargs_parse_delim(const char *args,
const char *const valid_keys[],
const char *valid_ends);
diff --git a/lib/kvargs/version.map b/lib/kvargs/version.map
index a07166b4d2..75b13fcb78 100644
--- a/lib/kvargs/version.map
+++ b/lib/kvargs/version.map
@@ -4,6 +4,7 @@ DPDK_22 {
rte_kvargs_count;
rte_kvargs_free;
rte_kvargs_parse;
+ rte_kvargs_parse_delim;
rte_kvargs_process;
local: *;
@@ -12,7 +13,6 @@ DPDK_22 {
EXPERIMENTAL {
global:
- rte_kvargs_parse_delim;
rte_kvargs_strcmp;
# added in 21.05
--
2.30.2
next prev parent reply other threads:[~2021-09-29 21:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 15:57 [dpdk-dev] [PATCH 0/5] kvargs: promote or remove experimental api Olivier Matz
2021-09-24 15:57 ` [dpdk-dev] [PATCH 1/5] kvargs: promote delimited parsing as stable Olivier Matz
2021-09-24 15:57 ` [dpdk-dev] [PATCH 2/5] kvargs: promote get from key " Olivier Matz
2021-09-24 15:57 ` [dpdk-dev] [PATCH 3/5] kvargs: new function to get from key and value Olivier Matz
2021-09-24 15:57 ` [dpdk-dev] [PATCH 4/5] kvargs: remove experimental function to compare string Olivier Matz
2021-09-26 16:30 ` Olivier Matz
2021-09-24 15:57 ` [dpdk-dev] [PATCH 5/5] kvargs: fix comments style Olivier Matz
2021-09-25 7:02 ` [dpdk-dev] [PATCH 0/5] kvargs: promote or remove experimental api Xueming(Steven) Li
2021-09-29 21:39 ` [dpdk-dev] [PATCH v2 " Olivier Matz
2021-09-29 21:39 ` Olivier Matz [this message]
2021-09-29 21:39 ` [dpdk-dev] [PATCH v2 2/5] kvargs: promote get from key as stable Olivier Matz
2021-09-29 21:39 ` [dpdk-dev] [PATCH v2 3/5] kvargs: new function to get from key and value Olivier Matz
2021-09-29 21:39 ` [dpdk-dev] [PATCH v2 4/5] kvargs: remove experimental function to compare string Olivier Matz
2021-09-30 14:00 ` Olivier Matz
2021-09-30 15:19 ` David Marchand
2021-09-29 21:39 ` [dpdk-dev] [PATCH v2 5/5] kvargs: fix comments style Olivier Matz
2021-09-30 8:25 ` [dpdk-dev] [PATCH v2 0/5] kvargs: promote or remove experimental api David Marchand
2021-09-30 9:57 ` Kinsella, Ray
2021-09-30 16:19 ` 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=20210929213943.17817-2-olivier.matz@6wind.com \
--to=olivier.matz@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=grive@u256.net \
--cc=mdr@ashroe.eu \
--cc=xuemingl@nvidia.com \
/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).