Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Maxim Skokov <skokovmaksimevg@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw89: fix typos in comments, debug messages and struct field
Date: Mon, 7 Sep 2026 00:53:33 +0000	[thread overview]
Message-ID: <8094bfc474e34b2f826b9487e49bd601@realtek.com> (raw)
In-Reply-To: <20260904222548.19732-1-skokovmaksimevg@gmail.com>

Maxim Skokov <skokovmaksimevg@gmail.com> wrote:
> Correct several misspellings found by codespell:
> 
>   moniter   -> monitor     (struct rtw89_btc_wl_role_info_bpos field)
>   serach    -> search      (comment)
>   Unsupport -> Unsupported (error message)
>   nofity    -> notify      (comment)
>   updat     -> update      (debug message)
>   lagacy    -> legacy      (comment)
> 
> The renamed struct field has no users, so no further changes are
> needed. No functional changes.
> 
> Signed-off-by: Maxim Skokov <skokovmaksimevg@gmail.com>

Acked-by: Ping-Ke Shih <pkshih@realtek.com>


> ---
> 
> Notes:
>     Found with codespell. Patch prepared with AI assistance; all changes reviewed by me.

Add a tag like  Assisted-by: LLM codespell ?

Just reply this mail, no need to resend v2. 


  reply	other threads:[~2026-09-07  0:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 22:25 [PATCH] wifi: rtw89: fix typos in comments, debug messages and struct field Maxim Skokov
2026-09-07  0:53 ` Ping-Ke Shih [this message]
2026-09-07  4:00   ` Maxim Skokov
2026-09-07  4:20     ` Ping-Ke Shih
2026-09-07  4:43       ` Maxim Skokov
2026-09-08  6:34 ` Ping-Ke Shih

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=8094bfc474e34b2f826b9487e49bd601@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=skokovmaksimevg@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