From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: ophirmu@mellanox.com, ferruh.yigit@intel.com,
arybchenko@solarflare.com, ktraynor@redhat.com,
ian.stokes@intel.com
Subject: [dpdk-dev] [PATCH 0/2] remove experimental tag for hotplug API
Date: Thu, 1 Nov 2018 15:46:31 +0100 [thread overview]
Message-ID: <20181101144633.13429-1-thomas@monjalon.net> (raw)
There are new functions in 18.11 which are fixing some hotplug issues.
OVS would like to use them but do not want to allow experimental
functions.
As these are major functions, fixing some issues, and replacing
a deprecated function, an exception should be done.
Thomas Monjalon (2):
eal: remove experimental tag for probe/remove
ethdev: remove experimental tag for iterator API
lib/librte_eal/common/eal_common_dev.c | 4 ++--
lib/librte_eal/common/include/rte_dev.h | 10 ++--------
lib/librte_eal/rte_eal_version.map | 4 ++--
lib/librte_ethdev/rte_ethdev.c | 6 +++---
lib/librte_ethdev/rte_ethdev.h | 12 ------------
lib/librte_ethdev/rte_ethdev_version.map | 6 +++---
6 files changed, 12 insertions(+), 30 deletions(-)
--
2.19.0
next reply other threads:[~2018-11-01 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 14:46 Thomas Monjalon [this message]
2018-11-01 14:46 ` [dpdk-dev] [PATCH 1/2] eal: remove experimental tag for probe/remove Thomas Monjalon
2018-11-05 12:19 ` Kevin Traynor
2018-11-05 13:13 ` Thomas Monjalon
2018-11-05 23:08 ` Thomas Monjalon
2018-11-01 14:46 ` [dpdk-dev] [PATCH 2/2] ethdev: remove experimental tag for iterator API Thomas Monjalon
2018-11-05 12:22 ` Kevin Traynor
2018-11-05 11:34 ` [dpdk-dev] [PATCH 0/2] remove experimental tag for hotplug API 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=20181101144633.13429-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ian.stokes@intel.com \
--cc=ktraynor@redhat.com \
--cc=ophirmu@mellanox.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).