From: Andrew Morton <akpm@linux-foundation.org>
To: Shuah Khan <shuahkhan@gmail.com>
Cc: Joe Perches <joe@perches.com>,
Peter Hurley <peter@hurleysoftware.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Improve CamelCase test for Page
Date: Fri, 22 Feb 2013 15:08:47 -0800 [thread overview]
Message-ID: <20130222150847.4562266b.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAKocOONj+gEcBXZJXGqoY00mcUf5WpLo7j7JF-S20UZED+pLCA@mail.gmail.com>
On Fri, 22 Feb 2013 15:57:16 -0700
Shuah Khan <shuahkhan@gmail.com> wrote:
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > index 747bcd7..e08e9f6 100755
> > --- a/scripts/checkpatch.pl
> > +++ b/scripts/checkpatch.pl
> > @@ -2929,8 +2929,8 @@ sub process {
> > while ($line =~ m{($Constant|$Lval)}g) {
> > my $var = $1;
> > if ($var !~ /$Constant/ &&
> > - $var =~ /[A-Z]\w*[a-z]|[a-z]\w*[A-Z]/ &&
> > - $var !~ /^Page[A-Z]/ &&
> > + $var =~ /[A-Z][a-z]|[a-z][A-Z]/ &&
> > + $var !~ /"^(?:Clear|Set|TestClear|TestSet|)Page[A-Z]/ && &&
> > !defined $camelcase{$var}) {
> > $camelcase{$var} = 1;
> > WARN("CAMELCASE",
> >
> >
>
> What are the guidelines on camelcase warnings on patches. A recent one
> I ran into is on a variable in a structure and fixing it would require
> changing the original variable.
>
> WARNING: Avoid CamelCase: <cp->Header.SGList>
> #67: FILE: drivers/scsi/hpsa.c:1409:
> + cp->Header.SGList = 0;
>
> WARNING: Avoid CamelCase: <cp->Header.SGTotal>
> #68: FILE: drivers/scsi/hpsa.c:1410:
> + cp->Header.SGTotal = 0;
>
> total: 0 errors, 2 warnings, 11 lines checked
>
> One would have to change a large portion of the code to fix it. In
> such cases, do we ignore this warning?
Yes, ignore the warning. In my experience this is always the case,
and it happens often.
prev parent reply other threads:[~2013-02-22 23:08 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
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 [this message]
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=20130222150847.4562266b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=shuahkhan@gmail.com \
/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.