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

Guenter Roeck linux at roeck-us.net
Wed Sep 14 19:46:32 UTC 2016


On Wed, Sep 14, 2016 at 08:13:17AM -0700, Joe Perches wrote:
> On Wed, 2016-09-14 at 07:45 -0700, Guenter Roeck wrote:
> > On 09/14/2016 07:23 AM, Joe Perches wrote:
> > > So what would use propose instead?
> > Introduce .checkpatch ?
> 
> A generic .checkpatch.conf option already exists which is
> looked for in . then $HOME
> 
That isn't kept in the repository as far as I can see.

> Do you mean a directory based hierarchy of .checkpatch.conf
> files in the git tree so a maintainer could add something like:
> 
> $ cat include/trace/events/.checkpatch.conf
> --ignore=spacing
> 
> and that applies only to that directory?
> 
That might solve the problem. However,

> That might get confusing and have conflicting options
> on the command line.

... it currently has a different scope: It is expected to be used in a
local setting, not delivered as part of the repository. So it would not
help to declare that per-directory settings override global settings
since people expect the global settings to work.

But, yes, something like that might help.

Guenter


More information about the Ksummit-discuss mailing list