Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751527AbbBLQoc (ORCPT ); Thu, 12 Feb 2015 11:44:32 -0500 Received: from wolverine02.qualcomm.com ([199.106.114.251]:17801 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751459AbbBLQo2 (ORCPT ); Thu, 12 Feb 2015 11:44:28 -0500 X-IronPort-AV: E=McAfee;i="5600,1067,7709"; a="195286212" X-IronPort-AV: E=Sophos;i="5.09,565,1418112000"; d="scan'208";a="32372333" From: Kalle Valo To: Joe Perches CC: Richard Weinberger , Dan Carpenter , Andrew Morton , "devel@driverdev.osuosl.org" , , Greg KH , Bas Peters , LKML , Pushpendra Singh , , Sudip Mukherjee , Pavel Machek Subject: Re: checkpatch induced patches... References: <1423573373-820-1-git-send-email-pushpendra.singh@smartplayin.com> <1423573373-820-2-git-send-email-pushpendra.singh@smartplayin.com> <20150210141307.GB15593@sudip-PC> <20150211083328.GJ5206@mwanda> <1423647637.15343.16.camel@perches.com> <20150211105122.GN5206@mwanda> <1423677629.15343.18.camel@perches.com> <20150211183615.GQ5206@mwanda> <1423686025.15343.20.camel@perches.com> Date: Thu, 12 Feb 2015 18:44:09 +0200 In-Reply-To: <1423686025.15343.20.camel@perches.com> (Joe Perches's message of "Wed, 11 Feb 2015 12:20:25 -0800") Message-ID: <87mw4jjd0m.fsf@kamboji.qca.qualcomm.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanexm01a.na.qualcomm.com (10.85.0.81) To NALASEXR01G.na.qualcomm.com (10.49.56.53) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1506 Lines: 45 Joe Perches writes: > On Wed, 2015-02-11 at 21:02 +0100, Richard Weinberger wrote: >> On Wed, Feb 11, 2015 at 7:36 PM, Dan Carpenter wrote: >> > On Wed, Feb 11, 2015 at 10:00:29AM -0800, Joe Perches wrote: >> >> I'm half tempted to submit some patch like this to >> >> make it difficult to use checkpatch on files outside >> >> of drivers/staging. >> >> >> >> o Only allow checkpatch to be used with the -f/--file >> >> option for drivers/staging/ >> >> o Add an undocumented --force command line option >> > >> > Sure. We could try that. I once sent a patch to make -f generate a >> > warning about not wasting people's time, but this is also ok. >> > >> >> o Make --strict the default for drivers/staging >> > >> > Ack. >> >> FYI: We had already a heated debate on that topic. >> https://lkml.org/lkml/2014/7/17/415 > > Yeah, I remember. > > It's always a pleasure to chat with Borislav. > > This is basically a patch that implements my suggestion > in that thread. > > https://lkml.org/lkml/2014/7/17/427 > > I wonder if the undocumented --force option is acceptable > to Pavel and Kalle. I don't mind if I have to add --force to my scripts as long as checkpatch works similarly as before. -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/