From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id A42195A41 for ; Thu, 9 Apr 2015 21:17:04 +0200 (CEST) Received: from hmsreliant.think-freely.org ([2001:470:8:a08:7aac:c0ff:fec2:933b] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1YgHwi-0003NP-2r; Thu, 09 Apr 2015 15:17:02 -0400 Date: Thu, 9 Apr 2015 15:16:58 -0400 From: Neil Horman To: Jay Rolette Message-ID: <20150409191658.GC26201@hmsreliant.think-freely.org> References: <3571725.20GtF5MAnU@xps13> <0C5AFCA4B3408848ADF2A3073F7D8CC86D58F9C2@IRSMSX109.ger.corp.intel.com> <20150408114339.GA22959@hmsreliant.think-freely.org> <0C5AFCA4B3408848ADF2A3073F7D8CC86D58FB64@IRSMSX109.ger.corp.intel.com> <20150408131105.GD22959@hmsreliant.think-freely.org> <0C5AFCA4B3408848ADF2A3073F7D8CC86D58FDBF@IRSMSX109.ger.corp.intel.com> <0FBA33A7-A21E-426F-B44E-32E86F2B23DB@infiniteio.com> <20150408153802.2bc59227@urahara> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Score: -2.9 (--) X-Spam-Status: No Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] tools brainstorming 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: Thu, 09 Apr 2015 19:17:04 -0000 On Thu, Apr 09, 2015 at 11:31:39AM -0500, Jay Rolette wrote: > On Wed, Apr 8, 2015 at 5:38 PM, Stephen Hemminger < > stephen@networkplumber.org> wrote: > > > On Wed, 8 Apr 2015 16:29:54 -0600 > > Jay Rolette wrote: > > > > > "C comments" includes //, right? It's been part of the C standard for a > > long time now... > > > > Yes but. > > I like to use checkpatch and checkpatch enforces kernel style which does > > not allow // for > > comments. > > > > Fork checkpatch and disable that bit? DPDK isn't the kernel, so no > requirement to follow all of its rules > Doesn't that beg the question, why? I understand the DPDK isn't the kernel, but we're not talking about clarity of code, not anything functional to that code. It seems we would be better served by just taking something that works here rather than re-inventing the wheel and digging into the minuate of what type of comments should be allowed (unless there is a compelling reason to change it that supercedes the avilable tools). If not checkpath, then some other tool, but It seems to me that coding style is one of those things where we can bend to the tool rather than taking the time to make the tool do exactly whats desired, at least until someone gets the time to modify it. Neil