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 3AAEB2A5E for ; Mon, 27 Feb 2017 18:06:26 +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 v1RH6Pdr026196 (version=TLSv1 cipher=AES128-SHA bits=128 verify=OK); Mon, 27 Feb 2017 09:06:25 -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; Mon, 27 Feb 2017 09:06:24 -0800 From: "Legacy, Allain" To: Stephen Hemminger CC: "YIGIT, FERRUH" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v2 11/15] net/avp: packet receive functions Thread-Index: AQHSkRkJUdZo+3bKWkqLSeNTIYglCKF9EErA Date: Mon, 27 Feb 2017 17:06:24 +0000 Message-ID: <70A7408C6E1BFB41B192A929744D85238A757FBC@ALA-MBC.corp.ad.wrs.com> References: <1487985795-136044-1-git-send-email-allain.legacy@windriver.com> <1488136143-116389-1-git-send-email-allain.legacy@windriver.com> <1488136143-116389-12-git-send-email-allain.legacy@windriver.com> <20170227084615.7ff06316@xeon-e3> In-Reply-To: <20170227084615.7ff06316@xeon-e3> 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 v2 11/15] net/avp: packet receive functions 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: Mon, 27 Feb 2017 17:06:27 -0000 > -----Original Message----- > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > On Sun, 26 Feb 2017 14:08:59 -0500 > Allain Legacy wrote: >=20 > Try not to break error messages onto two lines, it makes it harder when a > user is trying to find the location of the error message with search tool= s That's our normal practice, but checkpatches.sh flagged them as warnings. = If these are acceptable exceptions to the tool then are there plans to pub= lish an exhaustive list of checkpatches.sh errors/warnings/checks that can = be ignored? Alternatively, are there plans to change the tools to ignore t= hese automatically and not flag them as issues. As a contributor it is di= fficult to tell what will be deemed acceptable and what will not (in some c= ases) so the default position is to fix all issues before submission.=20