From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Anup Sharma <anupnewsmail@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: rtl8723bs: hal: Fix spelling mistakes in comments
Date: Mon, 26 Dec 2022 20:52:05 +0700 [thread overview]
Message-ID: <Y6mnBSg6i5wMCKUV@debian.me> (raw)
In-Reply-To: <Y6mYdPlqIK1VgQ0Z@local>
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
On Mon, Dec 26, 2022 at 06:19:56PM +0530, Anup Sharma wrote:
> They are appear to be spelling mistakes, initially identified in a codespell report and never been addressed so far.
Then where is the report, and what are the reported diagnostics?
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-12-26 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 12:49 [PATCH] staging: rtl8723bs: hal: Fix spelling mistakes in comments Anup Sharma
2022-12-26 13:52 ` Bagas Sanjaya [this message]
2022-12-26 17:08 ` Anup Sharma
2022-12-27 1:51 ` Bagas Sanjaya
2022-12-29 8:42 ` Dan Carpenter
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=Y6mnBSg6i5wMCKUV@debian.me \
--to=bagasdotme@gmail.com \
--cc=anupnewsmail@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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.