linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jonathan Corbet <corbet@lwn.net>, Kees Cook <keescook@chromium.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jiri Kosina <jikos@kernel.org>
Subject: Re: [PATCH] docs: fix "interruptible" misspellings
Date: Thu, 09 Jun 2016 13:11:42 -0700	[thread overview]
Message-ID: <1465503102.25087.79.camel@perches.com> (raw)
In-Reply-To: <20160609132937.3511e494@lwn.net>

On Thu, 2016-06-09 at 13:29 -0600, Jonathan Corbet wrote:
> On Wed, 18 May 2016 06:55:45 -0700 Kees Cook <keescook@chromium.org> wrote:
> > A common misspelling of "interruptible" is "interruptable". This fixes
> > them in the tree and adds the two most common variations to spelling.txt.

$ grep --include=*.[ch] -Proh "\b[A-Za-z]+[ai]ble\b" * | \
  tr [:upper:] [:lower:] | sort | uniq

gives several more that could be updated like:

avaiable
avaialable
avaible
available
availible
availlable
avalable
avalaible
avaliable
avalible
avalilable
aviable
avialable
avilable
[]
preemptable
preemptible
preemtible
[]
responsable
responsible
resposible
[]
unwritable
unwriteable
unwrittable
updatable
updateable
upgradable
upgradeable

  reply	other threads:[~2016-06-09 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 13:55 [PATCH] docs: fix "interruptible" misspellings Kees Cook
2016-06-09 19:29 ` Jonathan Corbet
2016-06-09 20:11   ` Joe Perches [this message]
2017-01-05 22:21     ` Kees Cook
2017-01-06  0:44       ` Randy Dunlap
2017-01-05 22:21   ` 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=1465503102.25087.79.camel@perches.com \
    --to=joe@perches.com \
    --cc=corbet@lwn.net \
    --cc=jikos@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).