From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH v2 08/15] net/ifc: rename to ifcvf Date: Wed, 13 Jun 2018 11:19:31 +0100 Message-ID: <20180613101930.GA9784@bricha3-MOBL.ger.corp.intel.com> References: <20180517201526.28658-1-bruce.richardson@intel.com> <20180608212048.67261-1-bruce.richardson@intel.com> <20180608212048.67261-9-bruce.richardson@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev@dpdk.org" To: "Wang, Xiao W" Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 01E0E1EC86 for ; Wed, 13 Jun 2018 12:19:38 +0200 (CEST) Content-Disposition: inline In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, Jun 13, 2018 at 03:46:05AM +0100, Wang, Xiao W wrote: > Hi Bruce, > > > -----Original Message----- > > From: Richardson, Bruce > > Sent: Saturday, June 9, 2018 5:21 AM > > To: dev@dpdk.org > > Cc: Richardson, Bruce ; Wang, Xiao W > > > > Subject: [PATCH v2 08/15] net/ifc: rename to ifcvf > > > > All files in the directory and the resulting driver have prefix of ifcvf, > > not just ifc, so rename directory for accuracy. Also rename the map file > > to standard name for meson build in the process. > > Compared with renaming the dir to IFCVF and renaming it back to IFC sometime in future, > I think keeping the dir name as IFC is better for us, this avoids the extra effort. > We can just rename below files: > doc/guides/nics/ifcvf.rst => doc/guides/nics/ifc.rst > drivers/net/ifc/rte_ifcvf_version.map => drivers/net/ifc/rte_pmd_ifc_version. > > And yes, we need to update documents which refer to ifc. > > Thanks! > Xiao > Ok, that can work.