All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Kees Cook <keescook@chromium.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Whitcroft <apw@canonical.com>,
	Masanari Iida <standby24x7@gmail.com>,
	linux-doc <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v2] checkpatch: look for common misspellings
Date: Thu, 11 Sep 2014 07:15:57 -0700	[thread overview]
Message-ID: <1410444957.9942.3.camel@joe-AO725> (raw)
In-Reply-To: <CAMuHMdUvBdEKCYezARJ8PvuQPQbi+Wq-fwO+Z2cxYXOtVzp5GQ@mail.gmail.com>

On Thu, 2014-09-11 at 09:19 +0200, Geert Uytterhoeven wrote:
> On Thu, Sep 11, 2014 at 12:52 AM, Andrew Morton
> <akpm@linux-foundation.org> wrote:
> > On Mon, 8 Sep 2014 11:15:24 -0700 Kees Cook <keescook@chromium.org> wrote:
> >> Check for misspellings, based on Debian's lintian list. Several false
> >> positives were removed, and several additional words added that were
[]
> > 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).

I'm a little concerned about false positives if that's
done, but it seems simple enough.

Maybe both of:

codespell:	/usr/share/codespell/dictionary.txt
lintian:	/usr/share/lintian/data/spelling/corrections




  parent reply	other threads:[~2014-09-11 14:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 18:15 [PATCH v2] checkpatch: look for common misspellings Kees Cook
2014-09-08 18:48 ` Joe Perches
2014-09-10  4:37   ` Masanari Iida
2014-09-10  7:00     ` Joe Perches
2014-09-10 22:52 ` Andrew Morton
2014-09-11  2:10   ` Joe Perches
2014-09-11  7:19   ` Geert Uytterhoeven
2014-09-11 14:12     ` Kees Cook
2014-09-11 14:15     ` Joe Perches [this message]
2014-09-12  4:09       ` Masanari Iida
2014-09-12  4:45         ` Joe Perches
2014-09-12 10:30           ` Masanari Iida

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=1410444957.9942.3.camel@joe-AO725 \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=geert@linux-m68k.org \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.