From: Randy Dunlap <rdunlap@infradead.org>
To: "Joe Perches" <joe@perches.com>, "Wang Qing" <wangqing@vivo.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Colin Ian King" <colin.king@canonical.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"David Hildenbrand" <david@redhat.com>,
"SeongJae Park" <sjpark@amazon.de>, Xiong <xndchn@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts: increase error-prone spell checking
Date: Tue, 22 Sep 2020 11:49:02 -0700 [thread overview]
Message-ID: <9e872477-4fb2-bf37-df76-bc6fd3f2972b@infradead.org> (raw)
In-Reply-To: <5c108605003d8ee48665ce616ec31c599c7f0c39.camel@perches.com>
On 9/22/20 9:00 AM, Joe Perches wrote:
> On Tue, 2020-09-22 at 07:37 -0700, Randy Dunlap wrote:
>> On 9/22/20 4:18 AM, Wang Qing wrote:
>>> Increase direcly,ununsed,manger spelling error check
>>>
>>> Signed-off-by: Wang Qing <wangqing@vivo.com>
>>> ---
>>> scripts/spelling.txt | 3 +++
>>> 1 file changed, 3 insertions(+)
>>>
>>> diff --git a/scripts/spelling.txt b/scripts/spelling.txt
>>> index f253681..91ab82b
>>> --- a/scripts/spelling.txt
>>> +++ b/scripts/spelling.txt
>>> @@ -1534,3 +1534,6 @@ writting||writing
>>> wtih||with
>>> zombe||zombie
>>> zomebie||zombie
>>> +direcly||directly
>>> +ununsed||unused
>>> +manger||manager
>>> \ No newline at end of file
>>>
>>
>> Uh, that file was in alphabetical order. Please try to keep it that way.
>
> More or less, but not completely.
> It's somewhat grouped by desired correction,
> but it's also somewhat random.
OK. Thanks for that.
> Here's a sorted diff:
> ---
> scripts/spelling.txt | 204 +++++++++++++++++++++++++--------------------------
> 1 file changed, 102 insertions(+), 102 deletions(-)
--
~Randy
prev parent reply other threads:[~2020-09-22 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 11:18 [PATCH] scripts: increase error-prone spell checking Wang Qing
2020-09-22 14:37 ` Randy Dunlap
2020-09-22 16:00 ` Joe Perches
2020-09-22 18:49 ` Randy Dunlap [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=9e872477-4fb2-bf37-df76-bc6fd3f2972b@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=david@redhat.com \
--cc=j.neuschaefer@gmx.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sjpark@amazon.de \
--cc=wangqing@vivo.com \
--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.