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 D3C091075 for ; Thu, 16 Mar 2017 16:33:56 +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 v2GFXoKv011153 (version=TLSv1 cipher=AES128-SHA bits=128 verify=OK); Thu, 16 Mar 2017 08:33:50 -0700 Received: from ALA-MBC.corp.ad.wrs.com ([fe80::fcbe:9b7:1141:89a1]) by ALA-HCB.corp.ad.wrs.com ([147.11.189.41]) with mapi id 14.03.0294.000; Thu, 16 Mar 2017 08:33:49 -0700 From: "Legacy, Allain" To: "YIGIT, FERRUH" CC: "dev@dpdk.org" , "Jolliffe, Ian" , "RICHARDSON, BRUCE" , "MCNAMARA, JOHN" , "WILES, ROGER" , "thomas.monjalon@6wind.com" , "vincent.jardin@6wind.com" , "jerin.jacob@caviumnetworks.com" , "stephen@networkplumber.org" , "3chas3@gmail.com" <3chas3@gmail.com> Thread-Topic: [PATCH v4 04/17] net/avp: add PMD version map file Thread-Index: AQHSnmUAOyQ/nVZbSE6Vd2SNHVb29qGXmHCQ Date: Thu, 16 Mar 2017 15:33:48 +0000 Message-ID: <70A7408C6E1BFB41B192A929744D8523968F24A6@ALA-MBC.corp.ad.wrs.com> References: <1488414008-162839-1-git-send-email-allain.legacy@windriver.com> <1489432593-32390-1-git-send-email-allain.legacy@windriver.com> <1489432593-32390-5-git-send-email-allain.legacy@windriver.com> In-Reply-To: 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 v4 04/17] net/avp: add PMD version map file 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, 16 Mar 2017 15:33:57 -0000 > -----Original Message----- > From: Ferruh Yigit [mailto:ferruh.yigit@intel.com] > Sent: Thursday, March 16, 2017 10:53 AM <..> =20 > Hi Allain, >=20 > Instead of adding files per patch, may I suggest different ordering: > First add skeleton files in a patch, later add functional pieces one by o= ne, like: >=20 > Merge patch 1/17, 3/17, this patch (4/17), 6/17 (removing SYMLINK), into > single patch and make it AVP first patch. This will be skeleton patch. >=20 > Second patch can be introducing public headers (2/17) and updating Makefi= le > to include them. >=20 > Third, debug log patch (5/17) >=20 > Patch 7/17 and later can stay same. >=20 > What do you think? Sure, I can give that a go and see what it looks like.