From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: <tomasz.unger@yahoo.pl>, <gregkh@linuxfoundation.org>
Cc: <dan.carpenter@linaro.org>, <linux-staging@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8723bs: Fix spelling mistakes in comments
Date: Fri, 20 Feb 2026 12:14:20 -0600 [thread overview]
Message-ID: <DGJZS1M87UBU.2JA0KERUBN6OP@gmail.com> (raw)
In-Reply-To: <20260220131647.1922405-1-tomasz.unger@yahoo.pl>
On Fri Feb 20, 2026 at 7:16 AM CST, tomasz.unger wrote:
> From: Tomasz Unger <tomasz.unger@yahoo.pl>
>
> 'alloction' -> 'allocation'
> 'overwirte' -> 'overwrite'
> 'indx' -> 'index'
>
> Found by manual inspection.
You don't have to write this, only say if you used a tool and what tool
it was. With that said... there are better ways to find spelling
mistakes than manual inspection, look into codespell.
>
> Signed-off-by: Tomasz Unger <tomasz.unger@yahoo.pl>
> ---
...
> if (i >= 0) {
> - /* Fix issue that pairwise and group key have same key id. Pairwise key first, group key can overwirte group only(ex: rekey) */
> + /* Fix issue that pairwise and group key have same key id. Pairwise key first, group key can overwrite group only(ex: rekey) */
While you're here, go ahead and turn this into a multi-line comment. If
unsure how, look in "Documentation/process/coding-style.rst".
Thanks,
ET
prev parent reply other threads:[~2026-02-20 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260220131647.1922405-1-tomasz.unger.ref@yahoo.pl>
2026-02-20 13:16 ` [PATCH] staging: rtl8723bs: Fix spelling mistakes in comments tomasz.unger
2026-02-20 18:14 ` Ethan Tidmore [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=DGJZS1M87UBU.2JA0KERUBN6OP@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=tomasz.unger@yahoo.pl \
/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