From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH 1/2] hexdump: whitespace cleanup
Date: Thu, 16 Aug 2018 09:59:41 -0700
Message-ID: <20180816095941.5acf7dbe@xeon-e3>
References: <20180816153106.7608-1-stephen@networkplumber.org>
 <20180816153106.7608-2-stephen@networkplumber.org>
 <C7B533E5-6755-4F52-BA8E-21E5022EF581@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>
To: "Wiles, Keith" <keith.wiles@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pl0-f66.google.com (mail-pl0-f66.google.com
 [209.85.160.66]) by dpdk.org (Postfix) with ESMTP id 720304C6F
 for <dev@dpdk.org>; Thu, 16 Aug 2018 18:59:44 +0200 (CEST)
Received: by mail-pl0-f66.google.com with SMTP id d5-v6so2384476pll.4
 for <dev@dpdk.org>; Thu, 16 Aug 2018 09:59:44 -0700 (PDT)
In-Reply-To: <C7B533E5-6755-4F52-BA8E-21E5022EF581@intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Thu, 16 Aug 2018 16:34:12 +0000
"Wiles, Keith" <keith.wiles@intel.com> wrote:

> I looked at the Coding Guide in section 1.7.2 and it states
> 
> 1.7.2. Definitions
> 	- The function type should be on a line by itself preceding the function.
> 	- The opening brace of the function body should be on a line by itself.
> 
> 	static char *
> 	function(int a1, int a2, float fl, int a4)
> 	{


Really, I thought in general DPDK followed Linux kernel style.
Making little exceptions like this is a nuisance.