From: Jens Axboe <axboe@kernel.dk>
To: Tom Saeger <tom.saeger@oracle.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
rdunlap@infradead.org, Bhaskar Chowdhury <unixbhaskar@gmail.com>
Subject: Re: [PATCH 1/1] block: fix trivial typos in comments
Date: Fri, 26 Mar 2021 09:46:36 -0600 [thread overview]
Message-ID: <02e3bdd7-896c-2286-d090-1931c5cd807e@kernel.dk> (raw)
In-Reply-To: <20210326154519.y2ztm2fqirxejaht@dhcp-10-154-182-208.vpn.oracle.com>
On 3/26/21 9:45 AM, Tom Saeger wrote:
> On Fri, Mar 26, 2021 at 09:41:49AM -0600, Jens Axboe wrote:
>> On 3/25/21 9:04 PM, Tom Saeger wrote:
>>>
>>> s/Additonal/Additional/
>>> s/assocaited/associated/
>>> s/assocaited/associated/
>>> s/assocating/associating/
>>> s/becasue/because/
>>> s/configred/configured/
>>> s/deactive/deactivate/
>>> s/followings/following/
>>> s/funtion/function/
>>> s/heirarchy/hierarchy/
>>> s/intiailized/initialized/
>>> s/prefered/preferred/
>>> s/readded/read/
>>> s/Secion/Section/
>>> s/soley/solely/
>>
>> While I'm generally happy to accept any patch that makes sense, the
>> recent influx of speling fixes have me less than excited. They just
>> add complications to backports and stable patches, for example, and
>> I'd prefer not to take them for that reason alone.
>
> Nod.
>
> In that case - perhaps adding these entries to scripts/spelling.txt
> would at least catch some going forward?
>
> I can send that.
That seems like a good idea.
--
Jens Axboe
next prev parent reply other threads:[~2021-03-26 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 3:04 [PATCH 1/1] block: fix trivial typos in comments Tom Saeger
2021-03-26 15:41 ` Jens Axboe
2021-03-26 15:45 ` Tom Saeger
2021-03-26 15:46 ` Jens Axboe [this message]
2021-03-29 18:13 ` Tom Saeger
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=02e3bdd7-896c-2286-d090-1931c5cd807e@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=tom.saeger@oracle.com \
--cc=unixbhaskar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox