From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Andrew Morton <akpm@linux-foundation.org>,
netdev <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] lib/test: Fix spelling mistakes
Date: Mon, 7 Jun 2021 17:18:59 +0800 [thread overview]
Message-ID: <769f678b-4501-87a8-98ca-708d0bb594b0@huawei.com> (raw)
In-Reply-To: <CAHp75VczLpKB4jnXO1be96nZYGrUWRwidj=LCLV=JuTqBpcM3g@mail.gmail.com>
On 2021/6/7 17:06, Andy Shevchenko wrote:
> On Mon, Jun 7, 2021 at 11:56 AM Leizhen (ThunderTown)
> <thunder.leizhen@huawei.com> wrote:
>> On 2021/6/7 16:52, Leizhen (ThunderTown) wrote:
>>> On 2021/6/7 16:39, Andy Shevchenko wrote:
>>>> On Mon, Jun 7, 2021 at 6:21 AM Zhen Lei <thunder.leizhen@huawei.com> wrote:
>>>>
>>>>> Fix some spelling mistakes in comments:
>>>>> thats ==> that's
>>>>> unitialized ==> uninitialized
>>>>> panicing ==> panicking
>>>>> sucess ==> success
>>>>> possitive ==> positive
>>>>> intepreted ==> interpreted
>>>>
>>>> Thanks for the fix! Is it done with the help of the codespell tool? If
>>>> not, can you run it and check if it suggests more fixes?
>>>
>>> Yes, it's detected by codespell tool. But to avoid too many changes in one patch, I tried
>>> breaking it down into smaller patches(If it can be classified) to make it easier to review.
>>> In fact, the other patch I just posted included the rest.
>>
>> https://lkml.org/lkml/2021/6/7/151
>>
>> All the remaining spelling mistakes are fixed by the patch above. I can combine the two of
>> them into one patch if you think it's necessary.
>
> No, it's good to keep them split. What I meant is to use the tool
> against the same subset of the files you have done your patch for. But
> please mention in the commit message that you have used that tool, so
> reviewers will not waste time on the comments like mine.
Okay, thanks for the advice.
>
>
next prev parent reply other threads:[~2021-06-07 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 3:15 [PATCH 1/1] lib/test: Fix spelling mistakes Zhen Lei
2021-06-07 8:39 ` Andy Shevchenko
2021-06-07 8:52 ` Leizhen (ThunderTown)
2021-06-07 8:56 ` Leizhen (ThunderTown)
2021-06-07 9:06 ` Andy Shevchenko
2021-06-07 9:18 ` Leizhen (ThunderTown) [this message]
2021-06-07 21:19 ` Andrey Konovalov
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=769f678b-4501-87a8-98ca-708d0bb594b0@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=andrii@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kasan-dev@googlegroups.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=ryabinin.a.a@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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).