From: Hemanth Selam <hemanth.selam@gmail.com>
To: Loic Poulain <loic.poulain@oss.qualcomm.com>
Cc: wcn36xx@lists.infradead.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] wifi: wcn36xx: fix typos in comments
Date: Mon, 7 Sep 2026 11:43:27 +0530 [thread overview]
Message-ID: <20260907061327.31452-1-hemanth.selam@gmail.com> (raw)
Fix typos in comments, reported by scripts/checkpatch.pl using the
misspelling list in scripts/spelling.txt. Only touches comments, no code
changes.
Assisted-by: Cursor:claude-opus-5
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
---
drivers/net/wireless/ath/wcn36xx/hal.h | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/net/wireless/ath/wcn36xx/hal.h b/drivers/net/wireless/ath/wcn36xx/hal.h
index ef9ea4ff891b..50c7b2ffb064 100644
--- a/drivers/net/wireless/ath/wcn36xx/hal.h
+++ b/drivers/net/wireless/ath/wcn36xx/hal.h
@@ -2650,7 +2650,7 @@ struct ani_global_class_a_stats_info {
* shall be the same as the supporteRates parameter. */
u32 rx_input_sensitivity;
- /* The maximum transmit power in dBm upto one decimal. for eg: if
+ /* The maximum transmit power in dBm up to one decimal. for eg: if
* it is 10.5dBm, the value would be 105 */
u32 max_pwr;
@@ -3133,7 +3133,7 @@ struct wcn36xx_hal_nv_img_download_req_msg {
/* Fragment sequence number of the NV Image. Note that NV Image
* might not fit into one message due to size limitation of the SMD
* channel FIFO. UMAC can hence choose to chop the NV blob into
- * multiple fragments starting with seqeunce number 0, 1, 2 etc.
+ * multiple fragments starting with sequence number 0, 1, 2 etc.
* The last fragment MUST be indicated by marking the
* isLastFragment field to 1. Note that all the NV blobs would be
* concatenated together by HAL without any padding bytes in
@@ -3275,7 +3275,7 @@ struct wcn36xx_hal_send_beacon_req_msg {
/* TIM IE offset from the beginning of the template. */
u32 tim_ie_offset;
- /* P2P IE offset from the begining of the template */
+ /* P2P IE offset from the beginning of the template */
u16 p2p_ie_offset;
} __packed;
@@ -4139,10 +4139,10 @@ struct wcn36xx_hal_dump_cmd_rsp_msg {
/* success or failure */
u32 status;
- /* Length of the responce message */
+ /* Length of the response message */
u32 rsp_length;
- /* FIXME: Currently considering the responce will be less than
+ /* FIXME: Currently considering the response will be less than
* 100bytes */
u8 rsp_buffer[DUMPCMD_RSP_BUFFER];
} __packed;
--
2.48.1
reply other threads:[~2026-09-07 6:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260907061327.31452-1-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=wcn36xx@lists.infradead.org \
/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®