From: Joe Perches <joe@perches.com>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
Cc: Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Andy Whitcroft <apw@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
Antti Palosaari <crope@iki.fi>,
Masanari Iida <standby24x7@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-doc <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: look for common misspellings
Date: Fri, 22 Aug 2014 16:22:42 -0700 [thread overview]
Message-ID: <1408749762.17241.50.camel@joe-AO725> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B402958C1CAFD@G9W0745.americas.hpqcorp.net>
On Fri, 2014-08-22 at 23:00 +0000, Elliott, Robert (Server Storage)
wrote:
> > From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> > owner@vger.kernel.org] On Behalf Of Joe Perches
> ...
> > +chang||change
>
> Although there are at least 2 misuses in the current kernel,
> that's also a fairly common name.
True. Thanks.
That one should likely be removed.
There are dozens of Chang name uses in the kernel.
I'm not attached at all to any of these btw.
Any others you think should not be used or
should be added?
One I thought kind of iffy was
contant||contact
Maybe that should be content instead.
Another thing the script might do is to check
if the $typo match is all upper case and then
substitute an all upper case $typo_fix.
It's also kind of noisy when run using -f,
so maybe this test should be --strict check with
files and a warning with patches.
next prev parent reply other threads:[~2014-08-22 23:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 16:20 Kees Cook
2014-08-21 17:18 ` Joe Perches
2014-08-21 23:01 ` Kees Cook
2014-08-22 0:10 ` Joe Perches
2014-08-22 22:37 ` Joe Perches
2014-08-22 23:00 ` Elliott, Robert (Server Storage)
2014-08-22 23:22 ` Joe Perches [this message]
2014-08-22 23:31 ` Kees Cook
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=1408749762.17241.50.camel@joe-AO725 \
--to=joe@perches.com \
--cc=Elliott@hp.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=crope@iki.fi \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=standby24x7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®