From: Guenter Roeck <linux@roeck-us.net>
To: Joe Perches <joe@perches.com>
Cc: ksummit-discuss@lists.linux-foundation.org,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] checkpatch/Codingstyle and trivial patch spam
Date: Wed, 14 Sep 2016 12:46:32 -0700 [thread overview]
Message-ID: <20160914194632.GA16397@roeck-us.net> (raw)
In-Reply-To: <1473865997.32273.36.camel@perches.com>
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
next prev parent reply other threads:[~2016-09-14 19:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 18:58 [Ksummit-discuss] [CORE TOPIC] checkpatch/Codingstyle and trivial patch spam Christian Borntraeger
2016-09-13 19:18 ` Joe Perches
2016-09-13 19:45 ` Josh Triplett
2016-09-13 20:03 ` Jonathan Corbet
2016-09-13 22:14 ` Joe Perches
2016-09-14 5:29 ` Julia Lawall
2016-09-13 23:49 ` Rafael J. Wysocki
2016-09-14 2:03 ` Josh Triplett
2016-09-14 2:24 ` Joe Perches
2016-09-14 5:57 ` Julia Lawall
2016-09-14 6:27 ` Joe Perches
2016-09-14 6:35 ` Julia Lawall
2016-09-14 6:43 ` Joe Perches
2016-09-14 17:11 ` Alexandre Belloni
2016-09-15 16:33 ` Jonathan Cameron
2016-09-14 11:54 ` Greg KH
2016-09-14 14:23 ` Joe Perches
2016-09-14 14:32 ` Greg KH
2016-09-14 14:35 ` Julia Lawall
2016-09-14 14:39 ` Theodore Ts'o
2016-09-14 19:26 ` Julia Lawall
2016-09-14 14:51 ` Joe Perches
2016-09-14 19:30 ` Julia Lawall
2016-09-14 14:51 ` Joe Perches
2016-09-14 14:45 ` Guenter Roeck
2016-09-14 15:13 ` Joe Perches
2016-09-14 19:46 ` Guenter Roeck [this message]
2016-09-14 18:04 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160914194632.GA16397@roeck-us.net \
--to=linux@roeck-us.net \
--cc=joe@perches.com \
--cc=ksummit-discuss@lists.linux-foundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.