From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v7 15/15] ethdev: Use embedded rte_device to detach driver Date: Thu, 29 Jun 2017 22:58:56 +0200 Message-ID: <41661112.fj3Og5vZkG@xps> References: <20170629182206.1072-1-jblunck@infradead.org> <20170629182206.1072-16-jblunck@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, gaetan.rivet@6wind.com, shreyansh.jain@nxp.com To: Jan Blunck Return-path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 3DA7A37A0 for ; Thu, 29 Jun 2017 22:58:58 +0200 (CEST) In-Reply-To: <20170629182206.1072-16-jblunck@infradead.org> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 29/06/2017 20:22, Jan Blunck: > --- a/lib/librte_eal/common/eal_common_dev.c > +++ b/lib/librte_eal/common/eal_common_dev.c > +int rte_eal_device_detach(struct rte_device *dev) [...] > int rte_eal_dev_detach(const char *name) I would be in favor of breaking the API without notice, and keep the name rte_eal_dev_detach for the function taking a rte_device as parameter. This function was introduced in 16.11 and has probably never been used, except in ethdev and testpmd. Legacy apps probably use rte_eth_dev_detach.