From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Zhen Lei <thunder.leizhen@huawei.com>,
Jason Baron <jbaron@akamai.com>,
Stefani Seibold <stefani@seibold.net>,
Jacob Keller <jacob.e.keller@intel.com>,
Thomas Graf <tgraf@suug.ch>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jens Axboe <axboe@kernel.dk>, 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>,
linux-block <linux-block@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] lib: Fix spelling mistakes
Date: Wed, 9 Jun 2021 17:33:29 +0200 [thread overview]
Message-ID: <eff5217f-74b5-3067-9210-6b2eb5ea5f4d@6wind.com> (raw)
In-Reply-To: <20210607072555.12416-1-thunder.leizhen@huawei.com>
Le 07/06/2021 à 09:25, Zhen Lei a écrit :
> Fix some spelling mistakes in comments:
> permanentely ==> permanently
> wont ==> won't
> remaning ==> remaining
> succed ==> succeed
> shouldnt ==> shouldn't
> alpha-numeric ==> alphanumeric
> storeing ==> storing
> funtion ==> function
> documenation ==> documentation
> Determin ==> Determine
> intepreted ==> interpreted
> ammount ==> amount
> obious ==> obvious
> interupts ==> interrupts
> occured ==> occurred
> asssociated ==> associated
> taking into acount ==> taking into account
> squence ==> sequence
> stil ==> still
> contiguos ==> contiguous
> matchs ==> matches
I don't know if there is already a patch flying somewhere, but it would be good
to add those typos in scripts/spelling.txt
Regards,
Nicolas
next prev parent reply other threads:[~2021-06-09 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 7:25 [PATCH 1/1] lib: Fix spelling mistakes Zhen Lei
2021-06-09 9:44 ` Keller, Jacob E
2021-06-09 15:33 ` Nicolas Dichtel [this message]
2021-06-10 1:01 ` Leizhen (ThunderTown)
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=eff5217f-74b5-3067-9210-6b2eb5ea5f4d@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=axboe@kernel.dk \
--cc=herbert@gondor.apana.org.au \
--cc=jacob.e.keller@intel.com \
--cc=jbaron@akamai.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=netdev@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=stefani@seibold.net \
--cc=tgraf@suug.ch \
--cc=thunder.leizhen@huawei.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).