From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 301662B92 for ; Fri, 9 Jun 2017 16:22:25 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga105.jf.intel.com with ESMTP; 09 Jun 2017 07:22:24 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,317,1493708400"; d="scan'208";a="1139642375" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.91]) ([10.237.220.91]) by orsmga001.jf.intel.com with ESMTP; 09 Jun 2017 07:22:21 -0700 To: Jan Blunck Cc: 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 , Thomas Monjalon , dev , Gaetan Rivet References: <20170526111502.92063-1-ferruh.yigit@intel.com> <20170606151008.62680-1-ferruh.yigit@intel.com> From: Ferruh Yigit Message-ID: <0b05d59f-f408-c42a-8d94-c0f8d09c7b2f@intel.com> Date: Fri, 9 Jun 2017 15:22:20 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v2] ethdev: remove driver name from device private data X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jun 2017 14:22:26 -0000 On 6/7/2017 5:11 PM, Jan Blunck wrote: > On Tue, Jun 6, 2017 at 5:10 PM, Ferruh Yigit wrote: >> 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 > > Acked-by: Jan Blunck Applied to dpdk-next-net/master, thanks.