From: Joe Perches <joe@perches.com>
To: Jilin Yuan <yuanjilin@cdjrlc.com>,
kvalo@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Cc: wcn36xx@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: wcn36xx: fix repeated words in comments
Date: Sat, 09 Jul 2022 12:07:10 -0700 [thread overview]
Message-ID: <b47293b4b8874c0ae32868533bd0df94e08b8706.camel@perches.com> (raw)
In-Reply-To: <20220709124356.52543-1-yuanjilin@cdjrlc.com>
On Sat, 2022-07-09 at 20:43 +0800, Jilin Yuan wrote:
> Delete the redundant word 'the'.
[]
> diff --git a/drivers/net/wireless/ath/wcn36xx/hal.h b/drivers/net/wireless/ath/wcn36xx/hal.h
[]
> @@ -1961,7 +1961,7 @@ struct wcn36xx_hal_config_bss_params {
>
> /* HAL should update the existing BSS entry, if this flag is set.
> * UMAC will set this flag in case of reassoc, where we want to
> - * resue the the old BSSID and still return success 0 = Add, 1 =
> + * resue the old BSSID and still return success 0 = Add, 1 =
s/resue/reuse/
> * Update */
> u8 action;
>
> @@ -2098,7 +2098,7 @@ struct wcn36xx_hal_config_bss_params_v1 {
>
> /* HAL should update the existing BSS entry, if this flag is set.
> * UMAC will set this flag in case of reassoc, where we want to
> - * resue the the old BSSID and still return success 0 = Add, 1 =
> + * resue the old BSSID and still return success 0 = Add, 1 =
here too
> * Update */
> u8 action;
>
> @@ -4142,7 +4142,7 @@ struct wcn36xx_hal_dump_cmd_rsp_msg {
> /* Length of the responce message */
> u32 rsp_length;
>
> - /* FIXME: Currently considering the the responce will be less than
> + /* FIXME: Currently considering the responce will be less than
s/responce/response/
> * 100bytes */
> u8 rsp_buffer[DUMPCMD_RSP_BUFFER];
> } __packed;
next prev parent reply other threads:[~2022-07-09 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 12:43 Jilin Yuan
2022-07-09 19:07 ` Joe Perches [this message]
2022-07-18 10:05 ` Kalle Valo
2022-09-15 3:04 Jilin Yuan
2022-09-19 12:43 ` Kalle Valo
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=b47293b4b8874c0ae32868533bd0df94e08b8706.camel@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wcn36xx@lists.infradead.org \
--cc=yuanjilin@cdjrlc.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®