kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Colin King <colin.king@canonical.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/spelling.txt: add more spelling mistakes to spelling.txt
Date: Mon, 18 Dec 2017 18:10:11 +0000	[thread overview]
Message-ID: <2cfeac9c-0592-3866-434f-f1dfc5dd33a9@infradead.org> (raw)
In-Reply-To: <20171218141904.7488-1-colin.king@canonical.com>

On 12/18/2017 06:19 AM, 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 since
> October 2017
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  scripts/spelling.txt | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/scripts/spelling.txt b/scripts/spelling.txt
> index 9a058cff49d4..7b3997e1eb4b 100644
> --- a/scripts/spelling.txt
> +++ b/scripts/spelling.txt


Hi Colin,

Please add:
assignement||assignment

thanks,
-- 
~Randy

  parent reply	other threads:[~2017-12-18 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 14:19 [PATCH] scripts/spelling.txt: add more spelling mistakes to spelling.txt Colin King
2017-12-18 17:49 ` Joe Perches
2017-12-18 17:53   ` Colin Ian King
2019-11-12  9:21   ` [PATCH] scripts/spelling.txt: add more spellings " Colin King
2020-03-13 17:49   ` Colin King
2020-03-13 21:11     ` Joe Perches
2020-07-14  9:28   ` Colin King
2017-12-18 18:10 ` Randy Dunlap [this message]
2017-12-18 18:46   ` [PATCH] scripts/spelling.txt: add more spelling mistakes " Joe Perches

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=2cfeac9c-0592-3866-434f-f1dfc5dd33a9@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=colin.king@canonical.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).