From: Kevin Traynor <ktraynor@redhat.com>
To: cristian.dumitrescu@intel.com
Cc: dev@dpdk.org, Kevin Traynor <ktraynor@redhat.com>
Subject: [dpdk-dev] [PATCH] meter: remove experimental from profile APIs
Date: Wed, 1 Aug 2018 16:30:49 +0100 [thread overview]
Message-ID: <1533137449-23445-1-git-send-email-ktraynor@redhat.com> (raw)
As per guideline that new APIs must be experimental
for at least one release, it is now possible to remove
the experimental tag from:
rte_meter_srtcm_profile_config()
rte_meter_trtcm_profile_config()
Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
---
examples/qos_meter/Makefile | 1 -
examples/qos_meter/meson.build | 1 -
lib/librte_meter/rte_meter.c | 4 ++--
lib/librte_meter/rte_meter.h | 5 ++---
lib/librte_meter/rte_meter_version.map | 2 +-
5 files changed, 5 insertions(+), 8 deletions(-)
diff --git a/examples/qos_meter/Makefile b/examples/qos_meter/Makefile
index 6da2407..46341b1 100644
--- a/examples/qos_meter/Makefile
+++ b/examples/qos_meter/Makefile
@@ -51,5 +51,4 @@ RTE_TARGET ?= x86_64-native-linuxapp-gcc
include $(RTE_SDK)/mk/rte.vars.mk
-CFLAGS += -DALLOW_EXPERIMENTAL_API
CFLAGS += -O3
CFLAGS += $(WERROR_FLAGS)
diff --git a/examples/qos_meter/meson.build b/examples/qos_meter/meson.build
index 10cd4bc..ef7779f 100644
--- a/examples/qos_meter/meson.build
+++ b/examples/qos_meter/meson.build
@@ -8,5 +8,4 @@
deps += 'meter'
-allow_experimental_apis = true
sources = files(
'main.c', 'rte_policer.c'
diff --git a/lib/librte_meter/rte_meter.c b/lib/librte_meter/rte_meter.c
index 59af5ef..473f69a 100644
--- a/lib/librte_meter/rte_meter.c
+++ b/lib/librte_meter/rte_meter.c
@@ -31,5 +31,5 @@
}
-int __rte_experimental
+int
rte_meter_srtcm_profile_config(struct rte_meter_srtcm_profile *p,
struct rte_meter_srtcm_params *params)
@@ -69,5 +69,5 @@
}
-int __rte_experimental
+int
rte_meter_trtcm_profile_config(struct rte_meter_trtcm_profile *p,
struct rte_meter_trtcm_params *params)
diff --git a/lib/librte_meter/rte_meter.h b/lib/librte_meter/rte_meter.h
index 03d8056..58a0515 100644
--- a/lib/librte_meter/rte_meter.h
+++ b/lib/librte_meter/rte_meter.h
@@ -21,5 +21,4 @@
#include <stdint.h>
-#include <rte_compat.h>
/*
@@ -83,5 +82,5 @@ struct rte_meter_trtcm_params {
* 0 upon success, error code otherwise
*/
-int __rte_experimental
+int
rte_meter_srtcm_profile_config(struct rte_meter_srtcm_profile *p,
struct rte_meter_srtcm_params *params);
@@ -97,5 +96,5 @@ struct rte_meter_trtcm_params {
* 0 upon success, error code otherwise
*/
-int __rte_experimental
+int
rte_meter_trtcm_profile_config(struct rte_meter_trtcm_profile *p,
struct rte_meter_trtcm_params *params);
diff --git a/lib/librte_meter/rte_meter_version.map b/lib/librte_meter/rte_meter_version.map
index 9215d4c..cb79f0c 100644
--- a/lib/librte_meter/rte_meter_version.map
+++ b/lib/librte_meter/rte_meter_version.map
@@ -12,5 +12,5 @@ DPDK_2.0 {
};
-EXPERIMENTAL {
+DPDK_18.08 {
global:
--
1.8.3.1
next reply other threads:[~2018-08-01 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 15:30 Kevin Traynor [this message]
2018-08-01 15:35 ` Dumitrescu, Cristian
2018-08-05 23:16 ` 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=1533137449-23445-1-git-send-email-ktraynor@redhat.com \
--to=ktraynor@redhat.com \
--cc=cristian.dumitrescu@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;
as well as URLs for NNTP newsgroup(s).