[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jKndemuqx=uFXSSEgD9v2U4b4E8Eh6O=FFNw+GL7fixxA@mail.gmail.com>
Date: Thu, 11 Sep 2014 07:12:24 -0700
From: Kees Cook <keescook@...omium.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andy Whitcroft <apw@...onical.com>,
Joe Perches <joe@...ches.com>,
Masanari Iida <standby24x7@...il.com>,
linux-doc <linux-doc@...r.kernel.org>
Subject: Re: [PATCH v2] checkpatch: look for common misspellings
On Thu, Sep 11, 2014 at 12:19 AM, Geert Uytterhoeven
<geert@...ux-m68k.org> wrote:
> On Thu, Sep 11, 2014 at 12:52 AM, Andrew Morton
> <akpm@...ux-foundation.org> wrote:
>> On Mon, 8 Sep 2014 11:15:24 -0700 Kees Cook <keescook@...omium.org> wrote:
>>
>>> Check for misspellings, based on Debian's lintian list. Several false
>>> positives were removed, and several additional words added that were
>>> common in the kernel:
>>>
>>> backword backwords
>>> invalide valide
>>> recieves
>>> singed unsinged
>>>
>>> While going back and fixing existing spelling mistakes isn't a high
>>> priority, it'd be nice to try to catch them before they hit the tree.
>>
>> I have a feeling this is going to be a rat hole and that
>> scripts/spelling.txt will grow to consume the planet. Oh well, whatev.
>
> What about making checkpatch use the codespell dictionay if codespell
> is installed?
>
> Codespell is in Ubuntu 14.04LTS (but not in 12.04LTS).
It's probably not a bad idea, but given the level of pruning that's
been needed already to keep down the false positive rate, I'm nervous
about a larger "general" corpus.
-Kees
--
Kees Cook
Chrome OS Security
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists