Re: [Ksummit-discuss] [CORE TOPIC] checkpatch/Codingstyle and trivial patch spam

[Greg KH <greg@kroah.com>]

On Tue, Sep 13, 2016 at 07:24:22PM -0700, Joe Perches wrote:
> On Tue, 2016-09-13 at 19:03 -0700, Josh Triplett wrote:
> > "Do
> > not mass-reformat existing code, even if it doesn't follow these
> > guidelines; doing so creates noise in version control history and makes
> > patches fail to apply."
> 
> It also could be useful to somehow separate newer, more actively
> developed code from the old stuff that should remain more static.
> 
> Old code should really only get code improvements like API changes,
> size reductions, constifications, performance improvements and bug
> fixes.
> 
> Maybe change the MAINTAINERS sections S: entries to have more
> comprehensive descriptions of what types of changes are acceptable
> for each section.
> 
> Right now it's
> 
> S:	Supported
> or
> S:	Maintained
> 
> Or maybe add something like a new entry for what types of changes
> are acceptable with a default of "none"
> 
> C:	Whitespace and Style	

Ick, no, we have way too many things in the MAINTAINERS file as it is...

thanks,

greg k-h