From: Greg KH <gregkh@linuxfoundation.org>
To: Haowen Bai <baihaowen@meizu.com>
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
straube.linux@gmail.com, linux@roeck-us.net,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: r8188eu: Fix misspelling in comment
Date: Tue, 29 Mar 2022 16:52:00 +0200 [thread overview]
Message-ID: <YkMdEIMHrYBPGYzK@kroah.com> (raw)
In-Reply-To: <1647831314-25511-1-git-send-email-baihaowen@meizu.com>
On Mon, Mar 21, 2022 at 10:55:14AM +0800, Haowen Bai wrote:
> The original error is as below shows:
>
> CHECK: 'associcated' may be misspelled - perhaps 'associated'?
>
> Signed-off-by: Haowen Bai <baihaowen@meizu.com>
> ---
> drivers/staging/r8188eu/core/rtw_ap.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/r8188eu/core/rtw_ap.c b/drivers/staging/r8188eu/core/rtw_ap.c
> index 1675e2e..e02dd8e 100644
> --- a/drivers/staging/r8188eu/core/rtw_ap.c
> +++ b/drivers/staging/r8188eu/core/rtw_ap.c
> @@ -819,7 +819,7 @@ static int rtw_ht_operation_update(struct adapter *padapter)
>
> void associated_clients_update(struct adapter *padapter, u8 updated)
> {
> - /* update associcated stations cap. */
> + /* update associated stations cap. */
> if (updated) {
> struct list_head *phead, *plist;
> struct sta_info *psta = NULL;
> @@ -972,7 +972,7 @@ void bss_cap_update_on_sta_join(struct adapter *padapter, struct sta_info *psta)
> update_beacon(padapter, _HT_ADD_INFO_IE_, NULL, true);
> }
>
> - /* update associcated stations cap. */
> + /* update associated stations cap. */
> associated_clients_update(padapter, beacon_updated);
>
> DBG_88E("%s, updated =%d\n", __func__, beacon_updated);
> @@ -1036,7 +1036,7 @@ u8 bss_cap_update_on_sta_leave(struct adapter *padapter, struct sta_info *psta)
> update_beacon(padapter, _HT_ADD_INFO_IE_, NULL, true);
> }
>
> - /* update associcated stations cap. */
> + /* update associated stations cap. */
>
> DBG_88E("%s, updated =%d\n", __func__, beacon_updated);
>
> --
> 2.7.4
>
>
Does not apply to my tree :(
next prev parent reply other threads:[~2022-03-29 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 2:55 Haowen Bai
2022-03-29 14:52 ` Greg KH [this message]
2022-03-30 1:42 ` baihaowen
2022-03-30 6:23 Haowen Bai
2022-03-30 6:39 ` Greg Kroah-Hartman
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=YkMdEIMHrYBPGYzK@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=baihaowen@meizu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux@roeck-us.net \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@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
all inboxes | Powered by JetHome®