From: Joe Perches <joe@perches.com>
To: Colin King <colin.king@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Kees Cook <keescook@chromium.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/spelling.txt: add a bunch more spelling mistakes
Date: Wed, 21 Jun 2017 12:09:36 -0700 [thread overview]
Message-ID: <1498072176.3337.2.camel@perches.com> (raw)
In-Reply-To: <20170621142614.12529-1-colin.king@canonical.com>
On Wed, 2017-06-21 at 15:26 +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Here are some of the more spelling mistakes and typos that I've
> found while fixing up spelling mistakes in kernel error message
> text over the past several weeks.
thanks.
prev parent reply other threads:[~2017-06-21 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 14:26 [PATCH] scripts/spelling.txt: add a bunch more spelling mistakes Colin King
2017-06-21 17:36 ` Kees Cook
2017-06-21 19:09 ` Joe Perches [this message]
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=1498072176.3337.2.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=sboyd@codeaurora.org \
--cc=yamada.masahiro@socionext.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