From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3 3/4] eal: remove experimental flag of hotplug functions Date: Wed, 03 Oct 2018 10:42:57 +0200 Message-ID: <6399878.QKedUUF0h3@xps> References: <20180907222727.20521-1-thomas@monjalon.net> <20180928162144.1972-4-thomas@monjalon.net> <6205dfd2-e14f-94dd-c621-ed9313dc8fba@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, gaetan.rivet@6wind.com, ophirmu@mellanox.com, qi.z.zhang@intel.com, ktraynor@redhat.com, Neil Horman To: Ferruh Yigit Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 26DD754AE for ; Wed, 3 Oct 2018 10:43:01 +0200 (CEST) In-Reply-To: <6205dfd2-e14f-94dd-c621-ed9313dc8fba@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 02/10/2018 12:28, Ferruh Yigit: > On 9/28/2018 5:21 PM, Thomas Monjalon wrote: > > These functions are quite old and are the only available replacement > > for the deprecated attach/detach functions. > > > > Note: some new functions may (again) replace these hotplug functions, > > in future, with better parameters. > > > > Signed-off-by: Thomas Monjalon > > --- > > lib/librte_eal/common/eal_common_dev.c | 7 ++++--- > > lib/librte_eal/common/include/rte_dev.h | 11 ++--------- > > lib/librte_eal/rte_eal_version.map | 4 ++-- > > Can remove "-DALLOW_EXPERIMENTAL_API" (or "allow_experimental_apis = true" for > meson) from drivers/raw/ifpga_rawdev when these APIs are not experimental anymore. > For reference: https://patches.dpdk.org/patch/45836/ Yes we could remove this flag in this patch. But the next series would add it again: https://patches.dpdk.org/patch/45601/ So I think it is not worth for now. > It is easy to know when to add "-DALLOW_EXPERIMENTAL_API" but it is hard to know > when to remove one, some helper should be good there. Yes, we should try to clean up those flags regularly after each -rc1 release. But we don't have any tooling for that.