From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Legacy, Allain" Subject: Re: [PATCH 3/5] cfgfile: add support for unamed global section Date: Fri, 3 Mar 2017 11:15:08 +0000 Message-ID: <70A7408C6E1BFB41B192A929744D85238A75B198@ALA-MBC.corp.ad.wrs.com> References: <1488482971-170522-1-git-send-email-allain.legacy@windriver.com> <1488482971-170522-4-git-send-email-allain.legacy@windriver.com> <3EB4FA525960D640B5BDFFD6A3D8912652758055@IRSMSX108.ger.corp.intel.com> <70A7408C6E1BFB41B192A929744D85238A75B14F@ALA-MBC.corp.ad.wrs.com> <3EB4FA525960D640B5BDFFD6A3D89126527580A4@IRSMSX108.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" , "Jolliffe, Ian" To: "DUMITRESCU, CRISTIAN FLORIN" , "RICHARDSON, BRUCE" Return-path: Received: from mail5.wrs.com (mail5.windriver.com [192.103.53.11]) by dpdk.org (Postfix) with ESMTP id AFCD82B93 for ; Fri, 3 Mar 2017 12:15:11 +0100 (CET) Received: from ALA-HCB.corp.ad.wrs.com (ala-hcb.corp.ad.wrs.com [147.11.189.41]) by mail5.wrs.com (8.15.2/8.15.2) with ESMTPS id v23BFAZR029940 (version=TLSv1 cipher=AES128-SHA bits=128 verify=OK) for ; Fri, 3 Mar 2017 03:15:10 -0800 In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D89126527580A4@IRSMSX108.ger.corp.intel.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > -----Original Message----- > From: Dumitrescu, Cristian [mailto:cristian.dumitrescu@intel.com] >=20 > I am not totally against it, but IMO this option is a bit confusing. Agai= n, what's > wrong with user explicitly adding the GLOBAL section if needed? There's nothing wrong with using a global section. It is our preference t= o use this method because we need to support a legacy file format that need= s to be parsed by other non-DPDK applications. Those applications expect t= his format. =20