From: Dan Carpenter <error27@gmail.com>
To: Anup Sharma <anupnewsmail@gmail.com>
Cc: bagasdotme@gmail.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH v2] staging: rtl8723bs: hal: Fix codespell-reported spelling mistakes
Date: Thu, 29 Dec 2022 11:56:42 +0300 [thread overview]
Message-ID: <Y61WSt4vzTjhDFS5@kadam> (raw)
In-Reply-To: <Y605bbJ+gPtBFrAZ@local>
On Thu, Dec 29, 2022 at 12:23:33PM +0530, Anup Sharma wrote:
> They are appear to be spelling mistakes, initially identified in a codespell report and never been addressed so far.
You're going to need to wrap this line. It's too long. Run
scripts/checkpatch.pl on your patches before sending them.
>
> drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.c:656: regsiters ==> registers
> drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.c:1696: beacause ==> because
> drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.c:2092: Checl ==> Check
> drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.c:2513: checksume ==> checksum
> drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.c:2726: sequense ==> sequence
> drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.c:2780: vlaue ==> value
> drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.c:3409: equall ==> equal, equally
>
> Signed-off-by: Anup Sharma <anupnewsmail@gmail.com>
>
> Changes in v2:
> - Added codespell report to make the commit message more clearer.
> ---
^^^
You need to put the v2 note under this --- cut off marker.
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
v3 now.
regards,
dan carpenter
prev parent reply other threads:[~2022-12-29 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 6:53 [PATCH v2] staging: rtl8723bs: hal: Fix codespell-reported spelling mistakes Anup Sharma
2022-12-29 8:56 ` Dan Carpenter [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=Y61WSt4vzTjhDFS5@kadam \
--to=error27@gmail.com \
--cc=anupnewsmail@gmail.com \
--cc=bagasdotme@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.