From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 05C7FAD99 for ; Wed, 22 Jun 2016 01:29:01 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP; 21 Jun 2016 16:28:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,507,1459839600"; d="scan'208";a="992491977" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by fmsmga001.fm.intel.com with ESMTP; 21 Jun 2016 16:28:42 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.183]) by IRSMSX102.ger.corp.intel.com ([169.254.2.10]) with mapi id 14.03.0248.002; Wed, 22 Jun 2016 00:28:41 +0100 From: "Dumitrescu, Cristian" To: Thomas Monjalon CC: "dev@dpdk.org" , "Singh, Jasvinder" Thread-Topic: [dpdk-dev] [PATCH] ip_pipeline: fix parsing error in TM port section Thread-Index: AQHRx60jfwAqRDhilUuypDbzppi5qJ/0XLGAgAA8niA= Date: Tue, 21 Jun 2016 23:28:41 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912647A0B027@IRSMSX108.ger.corp.intel.com> References: <1466067875-165380-1-git-send-email-jasvinder.singh@intel.com> <19575533.UNkKiejxmv@xps13> In-Reply-To: <19575533.UNkKiejxmv@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzM3ZTg2YzgtYTQ2Ni00OTBlLThjMjAtNDhiMzU0OGU2MDhkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IndQMktYYjVQc3d4MFFEXC9BUlY1ZVZ0YytDRUMxcHFQSkFTU2dLYUMrWlhVPSJ9 x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] ip_pipeline: fix parsing error in TM port section X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2016 23:29:02 -0000 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Tuesday, June 21, 2016 9:49 PM > To: Dumitrescu, Cristian > Cc: dev@dpdk.org; Singh, Jasvinder > Subject: Re: [dpdk-dev] [PATCH] ip_pipeline: fix parsing error in TM port > section >=20 > 2016-06-16 10:04, Jasvinder Singh: > > Replace APP_PARAM_ADD_LINK_FOR_TXQ with > APP_PARAM_ADD_LINK_FOR_TM macro > > in TM (Traffic Manager) port section parsing function. This macro adds > > nic ports entry specified in TM port section of the application > > configuration file to the application parameters structure. > > > > Fixes: e5a1cd8a4847 ("examples/ip_pipeline: clean up configuration > parser") > > > > Signed-off-by: Jasvinder Singh > > Acked-by: Cristian Dumitrescu >=20 > Already fixed in 81d084dd2aa8 ("examples/ip_pipeline: support KNI") >=20 > Cristian, you should not ack a patch which do more than announced in > the title. This pipeline KNI patch do a lot of things without any > explanation for the fixes. > 1 explanation =3D 1 patch Yeah, there were several small issues to fix and several people spotted the= m at the same time. I agree we should do a better job at separating differe= nt fixes into different patches. Sorry about this.