From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id CBBEE995 for ; Mon, 29 Aug 2016 19:10:26 +0000 (UTC) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A5E0923A for ; Mon, 29 Aug 2016 19:10:25 +0000 (UTC) Date: Mon, 29 Aug 2016 12:10:20 -0700 From: Josh Triplett To: Dan Carpenter Message-ID: <20160829191020.GB27600@cloud> References: <1472330452.26978.23.camel@perches.com> <20160829190618.GF4180@mwanda> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160829190618.GF4180@mwanda> Cc: Joe Perches , Greg KH , Sasha Levin , ksummit-discuss@lists.linuxfoundation.org, LKML Subject: Re: [Ksummit-discuss] checkkpatch (in)sanity ? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, Aug 29, 2016 at 10:06:18PM +0300, Dan Carpenter wrote: > I would like a couple changes which you know already: > > 1) Get rid of PREFER_ETHER_ADDR_COPY and similar because the people who > send checkpatch.pl fixes aren't qualified to say when it's legal or not > so they sometimes introduce bugs. I do think we should have *something* that catches such things. Perhaps not checkpatch.pl, though. Perhaps a compiler plugin that generates additional warnings, and can perhaps use more global information to determine legality?