From: Peter Hurley <peter@hurleysoftware.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Joe Perches <joe@perches.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Improve CamelCase test for Page
Date: Fri, 22 Feb 2013 17:21:51 -0500 [thread overview]
Message-ID: <1361571711.10906.5.camel@thor.lan> (raw)
In-Reply-To: <20130222140556.509fbbee.akpm@linux-foundation.org>
On Fri, 2013-02-22 at 14:05 -0800, Andrew Morton wrote:
> On Fri, 22 Feb 2013 17:01:48 -0500
> Peter Hurley <peter@hurleysoftware.com> wrote:
>
> > On Fri, 2013-02-22 at 12:59 -0800, Joe Perches wrote:
> > > Add the ClearPage/SetPage/TestClearPage/TestSetPage
> > > variants to the not reported Page CamelCase variables.
> > >
> > > Signed-off-by: Joe Perches <joe@perches.com>
> > > ---
> > > scripts/checkpatch.pl | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > > index 747bcd7..8a32306 100755
> > > --- a/scripts/checkpatch.pl
> > > +++ b/scripts/checkpatch.pl
> > > @@ -2930,7 +2930,7 @@ sub process {
> > > my $var = $1;
> > > if ($var !~ /$Constant/ &&
> > > $var =~ /[A-Z]\w*[a-z]|[a-z]\w*[A-Z]/ &&
> > > - $var !~ /^Page[A-Z]/ &&
> > > + $var !~ /"^(?:Clear|Set|TestClear|TestSet|)Page[A-Z]/ &&
> > > !defined $camelcase{$var}) {
> > > $camelcase{$var} = 1;
> > > WARN("CAMELCASE",
> > >
> >
> > In a recent patch, checkpatch gave this warning.
> >
> > WARNING: Avoid CamelCase: <tty->SAK_work>
> > #35: FILE: drivers/tty/tty_io.c:1475:
> > + flush_work(&tty->SAK_work);
>
> If we start whitelisting these things, it will never end.
>
> My (cruelly spurned) suggestion for this check is to grep the affected
> files to see if the symbol is already present and if so, don't warn.
>
> Or just revert the whole thing. I get tons of camelcase warnings, and
> they're always unuseful/incorrect/ignored.
Oh. I didn't know the impetus (although I had seen the mm variance and
wondered :)
I don't have an opinion on this. It doesn't bother me, but I'm not my
own maintainer.
next prev parent reply other threads:[~2013-02-22 22:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 20:42 [merged] checkpatch-dont-emit-the-camelcase-warning-for-pagefoo.patch removed from -mm tree akpm
2013-02-22 20:59 ` [PATCH] checkpatch: Improve CamelCase test for Page Joe Perches
2013-02-22 22:01 ` Peter Hurley
2013-02-22 22:05 ` Andrew Morton
2013-02-22 22:21 ` Peter Hurley [this message]
2013-02-22 22:21 ` Joe Perches
2013-02-22 22:38 ` Peter Hurley
2013-02-22 22:57 ` Shuah Khan
2013-02-22 23:06 ` Joe Perches
2013-02-22 23:08 ` Andrew Morton
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=1361571711.10906.5.camel@thor.lan \
--to=peter@hurleysoftware.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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.