All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sjpark@amazon.com>
To: <dingsenjie@163.com>
Cc: <akpm@linux-foundation.org>, <colin.king@canonical.com>,
	<naoki.hayama@lineo.co.jp>, <xndchn@gmail.com>,
	<sjpark@amazon.de>, <ebiggers@google.com>, <joe@perches.com>,
	<linux-kernel@vger.kernel.org>,
	dingsenjie <dingsenjie@yulong.com>
Subject: Re: [PATCH] scripts/spelling.txt: increase error-prone spell checking
Date: Wed, 27 Jan 2021 08:47:16 +0100	[thread overview]
Message-ID: <20210127074716.25987-1-sjpark@amazon.com> (raw)
In-Reply-To: <20210127030105.7244-1-dingsenjie@163.com>

On Wed, 27 Jan 2021 11:01:05 +0800 dingsenjie@163.com wrote:

> From: dingsenjie <dingsenjie@yulong.com>
> 
> Increase allocted spelling error check.

I think you could improve the title and the commit message.  You could
refer to
https://lore.kernel.org/lkml/7937a406-812e-0a41-12c5-41576737a44f@lucaceresoli.net/

Thanks,
SeongJae Park

> 
> Signed-off-by: dingsenjie <dingsenjie@yulong.com>
> ---
>  scripts/spelling.txt | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/scripts/spelling.txt b/scripts/spelling.txt
> index 953f4a2..5fa8ec2 100644
> --- a/scripts/spelling.txt
> +++ b/scripts/spelling.txt
> @@ -103,6 +103,7 @@ alloated||allocated
>  allocatote||allocate
>  allocatrd||allocated
>  allocte||allocate
> +allocted||allocated
>  allpication||application
>  alocate||allocate
>  alogirhtms||algorithms
> -- 
> 1.9.1
> 

  reply	other threads:[~2021-01-27  7:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27  3:01 [PATCH] scripts/spelling.txt: increase error-prone spell checking dingsenjie
2021-01-27  7:47 ` SeongJae Park [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-27  6:00 zuoqilin1
2021-01-27  7:55 ` SeongJae Park
2021-01-21  2:07 ChunyouTang
2021-01-21  3:02 ` Randy Dunlap
2021-01-21  3:09   ` Joe Perches
     [not found]     ` <20210121112115.00005cb6@163.com>
2021-01-21  8:41       ` Luca Ceresoli
2021-01-21  9:14         ` Naoki Hayama
2021-01-21  9:36           ` Joe Perches
2021-01-21  9:49             ` Naoki Hayama

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=20210127074716.25987-1-sjpark@amazon.com \
    --to=sjpark@amazon.com \
    --cc=akpm@linux-foundation.org \
    --cc=colin.king@canonical.com \
    --cc=dingsenjie@163.com \
    --cc=dingsenjie@yulong.com \
    --cc=ebiggers@google.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naoki.hayama@lineo.co.jp \
    --cc=sjpark@amazon.de \
    --cc=xndchn@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.