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 4AA41305 for ; Mon, 20 Jul 2015 22:12:57 +0000 (UTC) Received: from bh-25.webhostbox.net (bh-25.webhostbox.net [208.91.199.152]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id EBA75129 for ; Mon, 20 Jul 2015 22:12:56 +0000 (UTC) Message-ID: <55AD7263.8050605@roeck-us.net> Date: Mon, 20 Jul 2015 15:12:51 -0700 From: Guenter Roeck MIME-Version: 1.0 To: Greg KH , Julia Lawall References: <20150717133712.42c82add@gandalf.local.home> <20150717190223.GB1499@cloud> <20150717154326.6f129bc4@gandalf.local.home> <20150717202412.GA1856@cloud> <20150717163903.67747d86@gandalf.local.home> <20150717204856.GA2048@cloud> <20150717165501.62ed4e04@gandalf.local.home> <1437376105.8968.14.camel@HansenPartnership.com> <20150720203007.GA7797@kroah.com> In-Reply-To: <20150720203007.GA7797@kroah.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: James Bottomley , Dan Carpenter , "ksummit-discuss@lists.linuxfoundation.org" , Jason Cooper Subject: Re: [Ksummit-discuss] [CORE TOPIC] Recruitment (Reviewers, Testers, Maintainers, Hobbyists) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 07/20/2015 01:30 PM, Greg KH wrote: >> If there really is a problem that some maintainer is getting inundated >> with patches addressing unimportant cosmetic issues, could it be a good >> idea to: >> >> * Fix the code and get it over with, >> * Drop the code from the kernel, if no one uses it, or >> * Put a comment in the file saying that the file is no longer being >> actively developed and only bug fixes will be accepted. > > I agree with this. If your subsystem is constantly getting hit with > coding style cleanups that you don't want (i.e. SCSI), put something in > the top of the file that says "don't clean up the style". > How about a cleanup tag in MAINTAINERS ? Then checkpatch could warn if it is used on a file tagged as do-not-clean, and every maintainer could set preferences as desired. Something like C: yes C: limited (prior to functional changes only) C: no Either limited or yes could be the default. The "Obsolete" status presumably implies that cleanups are not desired, and checkpatch could issue a warning if it is run on an obsolete file or subsystem. Guenter