From: <pbhagavatula@marvell.com>
To: <jerinj@marvell.com>, Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ray Kinsella <mdr@ashroe.eu>
Cc: <dev@dpdk.org>, Pavan Nikhilesh <pbhagavatula@marvell.com>
Subject: [dpdk-dev] [PATCH] ethdev: promote set ptypes API to stable
Date: Thu, 2 Sep 2021 13:47:30 +0530 [thread overview]
Message-ID: <20210902081731.2935-1-pbhagavatula@marvell.com> (raw)
From: Pavan Nikhilesh <pbhagavatula@marvell.com>
Remove experimental tag from rte_eth_dev_set_ptypes().
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
lib/ethdev/rte_ethdev.h | 4 ----
lib/ethdev/version.map | 2 +-
2 files changed, 1 insertion(+), 5 deletions(-)
diff --git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h
index d2b27c351f..55d0da60bd 100644
--- a/lib/ethdev/rte_ethdev.h
+++ b/lib/ethdev/rte_ethdev.h
@@ -3123,9 +3123,6 @@ int rte_eth_dev_fw_version_get(uint16_t port_id,
int rte_eth_dev_get_supported_ptypes(uint16_t port_id, uint32_t ptype_mask,
uint32_t *ptypes, int num);
/**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
* Inform Ethernet device about reduced range of packet types to handle.
*
* Application can use this function to set only specific ptypes that it's
@@ -3155,7 +3152,6 @@ int rte_eth_dev_get_supported_ptypes(uint16_t port_id, uint32_t ptype_mask,
* - (-EINVAL) if *ptype_mask* is invalid (or) set_ptypes is NULL and
* num > 0.
*/
-__rte_experimental
int rte_eth_dev_set_ptypes(uint16_t port_id, uint32_t ptype_mask,
uint32_t *set_ptypes, unsigned int num);
diff --git a/lib/ethdev/version.map b/lib/ethdev/version.map
index 3eece75b72..b02d981378 100644
--- a/lib/ethdev/version.map
+++ b/lib/ethdev/version.map
@@ -52,6 +52,7 @@ DPDK_22 {
rte_eth_dev_set_link_up;
rte_eth_dev_set_mc_addr_list;
rte_eth_dev_set_mtu;
+ rte_eth_dev_set_ptypes;
rte_eth_dev_set_rx_queue_stats_mapping;
rte_eth_dev_set_tx_queue_stats_mapping;
rte_eth_dev_set_vlan_ether_type;
@@ -173,7 +174,6 @@ EXPERIMENTAL {
rte_flow_dynf_metadata_offs;
rte_flow_dynf_metadata_mask;
rte_flow_dynf_metadata_register;
- rte_eth_dev_set_ptypes;
# added in 20.02
rte_flow_dev_dump;
--
2.17.1
next reply other threads:[~2021-09-02 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 8:17 pbhagavatula [this message]
2021-09-02 8:58 ` Andrew Rybchenko
2021-09-02 15:56 ` Kinsella, Ray
2021-09-15 8:15 ` Ferruh Yigit
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=20210902081731.2935-1-pbhagavatula@marvell.com \
--to=pbhagavatula@marvell.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=mdr@ashroe.eu \
--cc=thomas@monjalon.net \
/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).