From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 7809BC4C2 for ; Fri, 23 Oct 2015 11:08:29 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 23 Oct 2015 02:08:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,186,1444719600"; d="scan'208";a="800976737" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by orsmga001.jf.intel.com with ESMTP; 23 Oct 2015 02:08:28 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.116]) by IRSMSX153.ger.corp.intel.com ([169.254.9.191]) with mapi id 14.03.0248.002; Fri, 23 Oct 2015 10:08:27 +0100 From: "Mcnamara, John" To: mablexidana , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH] fix lpm bugs Thread-Index: AQHRC+aQyjwtY8bnS0W2xwxiXV8BDZ51uOCAgAD9igCAAe88gIAAIwKg Date: Fri, 23 Oct 2015 09:08:26 +0000 Message-ID: References: <5e5d9466.100a4.15089d2018f.Coremail.mablexidana@163.com> <20151021110749.GD16140@bricha3-MOBL3> <313921ca.4b27.1508d543038.Coremail.mablexidana@163.com> <29ae0ca8.e6db.15093aafa12.Coremail.mablexidana@163.com> In-Reply-To: <29ae0ca8.e6db.15093aafa12.Coremail.mablexidana@163.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: 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] fix lpm bugs 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: Fri, 23 Oct 2015 09:08:29 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of mablexidana > Sent: Friday, October 23, 2015 8:48 AM > To: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] fix lpm bugs >=20 > hi: > This is test on dpdk version 2.1 Hi, Thanks for that. The patch needs to be signed and isn't quite in the correc= t format. See the following for some quidelines on how to format/submit a patch. http://dpdk.org/dev/patchwork/patch/7762/ If you need some extra text to describe the test to describe the test setup= , etc., you can use the cover letter or a follow-up reply. The commit messa= ge should still contain the issue(s) that is fixed and how to re-produce it= . See the above doc for full details. John. -- =20