From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail5.wrs.com (mail5.windriver.com [192.103.53.11]) by dpdk.org (Postfix) with ESMTP id 0B1D42A5E for ; Thu, 2 Mar 2017 22:23:02 +0100 (CET) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail5.wrs.com (8.15.2/8.15.2) with ESMTPS id v22LN1gl010369 (version=TLSv1 cipher=AES128-SHA bits=128 verify=OK) for ; Thu, 2 Mar 2017 13:23:01 -0800 Received: from ALA-MBC.corp.ad.wrs.com ([fe80::fcbe:9b7:1141:89a1]) by ALA-HCA.corp.ad.wrs.com ([147.11.189.40]) with mapi id 14.03.0294.000; Thu, 2 Mar 2017 13:22:59 -0800 From: "Legacy, Allain" To: "RICHARDSON, BRUCE" CC: "DUMITRESCU, CRISTIAN FLORIN" , "dev@dpdk.org" , "Jolliffe, Ian" Thread-Topic: [PATCH 1/5] cfgfile: configurable comment character Thread-Index: AQHSk5lpFVKuCWJbrUeFRCC27PQYOKGCDvnA Date: Thu, 2 Mar 2017 21:22:59 +0000 Message-ID: <70A7408C6E1BFB41B192A929744D85238A75A938@ALA-MBC.corp.ad.wrs.com> References: <1488482971-170522-1-git-send-email-allain.legacy@windriver.com> <1488482971-170522-2-git-send-email-allain.legacy@windriver.com> <20170302211015.GA18940@bricha3-MOBL3.ger.corp.intel.com> In-Reply-To: <20170302211015.GA18940@bricha3-MOBL3.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.224.140.166] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 1/5] cfgfile: configurable comment character 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: Thu, 02 Mar 2017 21:23:03 -0000 > -----Original Message----- > From: Bruce Richardson [mailto:bruce.richardson@intel.com] > We are trying to avoid adding in extra build-time options to DPDK, so > can you please rework this patch to make it a run-time option instead. > Perhaps just add a set_comment_char() API call to the library. If this > is a setting per cfgfile instance it would then allow applications to > simultaneously use files with different formats. For example, if in > future we use cfgfile library to configure DPDK EAL, a preexisting file > for that shipped with DPDK may conflict in format with an > application-specific one. Ok, sounds reasonable.