From: Kees Cook <keescook@chromium.org>
To: Joe Perches <joe@perches.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jiri Kosina <jikos@kernel.org>
Subject: Re: [PATCH] docs: fix "interruptible" misspellings
Date: Thu, 5 Jan 2017 14:21:43 -0800 [thread overview]
Message-ID: <CAGXu5j+0KgOzOkHC2AOiR5JU_CH5=BPP+J0FZQbU6abNV7=BZQ@mail.gmail.com> (raw)
In-Reply-To: <1465503102.25087.79.camel@perches.com>
On Thu, Jun 9, 2016 at 1:11 PM, Joe Perches <joe@perches.com> wrote:
> 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
Oooh, yeah, these should get fixed too. Joe, do you have time to build
a full patch for them?
-Kees
--
Kees Cook
Nexus Security
next prev parent reply other threads:[~2017-01-05 22:22 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
2017-01-05 22:21 ` Kees Cook [this message]
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='CAGXu5j+0KgOzOkHC2AOiR5JU_CH5=BPP+J0FZQbU6abNV7=BZQ@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=corbet@lwn.net \
--cc=jikos@kernel.org \
--cc=joe@perches.com \
--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).