From: Konstantin Ananyev <konstantin.ananyev@intel.com>
To: dev@dpdk.org
Cc: mdr@ashroe.eu, Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-dev] [PATCH v2] ip_frag: promote APIs to stable
Date: Thu, 28 Oct 2021 12:51:00 +0100 [thread overview]
Message-ID: <20211028115100.10556-1-konstantin.ananyev@intel.com> (raw)
In-Reply-To: <20211018153619.31736-1-konstantin.ananyev@intel.com>
Promote rte_frag_table_del_expired_entries() function to stable.
It was around for few years by now without any changes.
Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
---
lib/ip_frag/rte_ip_frag.h | 1 -
lib/ip_frag/version.map | 7 +------
2 files changed, 1 insertion(+), 7 deletions(-)
diff --git a/lib/ip_frag/rte_ip_frag.h b/lib/ip_frag/rte_ip_frag.h
index 08555fde6a..d856f87e6c 100644
--- a/lib/ip_frag/rte_ip_frag.h
+++ b/lib/ip_frag/rte_ip_frag.h
@@ -326,7 +326,6 @@ rte_ip_frag_table_statistics_dump(FILE * f, const struct rte_ip_frag_tbl *tbl);
* @param tms
* Current timestamp
*/
-__rte_experimental
void
rte_frag_table_del_expired_entries(struct rte_ip_frag_tbl *tbl,
struct rte_ip_frag_death_row *dr, uint64_t tms);
diff --git a/lib/ip_frag/version.map b/lib/ip_frag/version.map
index 33f231fb31..2e13bef645 100644
--- a/lib/ip_frag/version.map
+++ b/lib/ip_frag/version.map
@@ -1,6 +1,7 @@
DPDK_22 {
global:
+ rte_frag_table_del_expired_entries;
rte_ip_frag_free_death_row;
rte_ip_frag_table_create;
rte_ip_frag_table_destroy;
@@ -12,9 +13,3 @@ DPDK_22 {
local: *;
};
-
-EXPERIMENTAL {
- global:
-
- rte_frag_table_del_expired_entries;
-};
--
2.26.3
next prev parent reply other threads:[~2021-10-28 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 15:36 [dpdk-dev] [PATCH] " Konstantin Ananyev
2021-10-20 9:39 ` Kinsella, Ray
2021-10-28 11:51 ` Konstantin Ananyev [this message]
2021-11-04 18:24 ` [dpdk-dev] [PATCH v2] " 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=20211028115100.10556-1-konstantin.ananyev@intel.com \
--to=konstantin.ananyev@intel.com \
--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).