From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933085AbcINSdy (ORCPT ); Wed, 14 Sep 2016 14:33:54 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:49101 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932517AbcINSdt (ORCPT ); Wed, 14 Sep 2016 14:33:49 -0400 X-Sasl-enc: trKlnvyg4MegoGSN8gm7T6lRjlbp4n3lyrrwl0uAoLw7 1473878027 Date: Wed, 14 Sep 2016 20:33:54 +0200 From: Greg KH To: Christian Borntraeger Cc: Joe Perches , Andrew Morton , Andy Whitcroft , Jonathan Corbet , Josh Triplett , "Theodore Ts'o" , linux-kernel@vger.kernel.org Subject: Re: [PATCH] checkpatch: Minimize checkpatch induced patches... Message-ID: <20160914183354.GA21814@kroah.com> References: <1473876366.32273.40.camel@perches.com> <554bcd26-f513-adf1-1a01-8b0ca9ff4aed@de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <554bcd26-f513-adf1-1a01-8b0ca9ff4aed@de.ibm.com> User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 14, 2016 at 08:16:55PM +0200, Christian Borntraeger wrote: > On 09/14/2016 08:06 PM, Joe Perches wrote: > > On Wed, 2016-09-14 at 19:56 +0200, Christian Borntraeger wrote: > > > >> This will certainly help to reduce the noise. On the other hand I remember Linus > >> saying something along the line that he does not like the -f parameter (and he > >> prefers to set this automatically). So while I like the approach I am not happy > >> enough to ack right now - still looking for a better alternative :-/ > > > > Linus likely hasn't used checkpatch in a decade or so. > > > > Taste and judgment can't be scripted anyway. > > > > Let me know if you find an alternative. > > You know what. > with some additional writing like > "Existing code outside staging is not supposed to be "fixed" to match checkpatch. > Please do not send checkpatch initiated patches for those files" > near the newly created warn That's not true, I _WANT_ checkpatch cleanups for the portion of the kernel I maintain. It keeps the code correct, up to date, easier to maintain, and in doing so, we have found real bugs over time. So don't make a blanket statement like that please. And I'd strongly suggest you revisit your feelings about this for code you maintain, unless you want it to bitrot and not get any new contributions or contributors :) thanks, greg k-h