From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] ethdev: remove driver name from device private data Date: Thu, 08 Jun 2017 22:58:02 +0200 Message-ID: <20233845.fUV38rRMBa@xps> References: <20170526111502.92063-1-ferruh.yigit@intel.com> <20170606151008.62680-1-ferruh.yigit@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Stephen Hurd , Ajit Khaparde , Declan Doherty , Rahul Lakkireddy , Hemant Agrawal , Shreyansh Jain , Helin Zhang , Jingjing Wu , Wenzhuo Lu , Konstantin Ananyev , Bruce Richardson , Pascal Mazon , Shrikrishna Khare , Jianfeng Tan , Gaetan Rivet , Jan Blunck To: Ferruh Yigit Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id E6A5B2BA1 for ; Thu, 8 Jun 2017 22:58:03 +0200 (CEST) In-Reply-To: <20170606151008.62680-1-ferruh.yigit@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" 06/06/2017 17:10, Ferruh Yigit: > rte_driver->name has the driver name and all physical and virtual > devices has access to it. > > Previously it was not possible for virtual ethernet devices to access > rte_driver->name field (because eth_dev used to keep only pci_dev), > and it was required to save driver name in the device private struct. > > After re-works on bus and vdev, it is possible for all bus types to > access rte_driver. > > It is able to remove the driver name from ethdev device private data and > use eth_dev->device->driver->name. > > Signed-off-by: Ferruh Yigit > --- > Cc: Gaetan Rivet > Cc: Jan Blunck > > v2: > * rebase on latest next-net This patch must be applied after merging next-net. Do you plan a pull request soon?