Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Chien Wong" <m@xv97.com>
To: "Jeff Johnson" <jeff.johnson@oss.qualcomm.com>,
	"Chien Wong" <m@xv97.com>,
	"'ath11k@lists.infradead.org'" <ath11k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wifi: ath: fix comment typo in monitor mode handling
Date: Thu, 15 Jan 2026 16:20:12 +0800	[thread overview]
Message-ID: <DFP0LJ1BX1US.2KD2FIIVAKD3S@xv97.com> (raw)
In-Reply-To: <a47cfe9f-01eb-4cdd-ac97-421f3c8a3451@oss.qualcomm.com>

On Thu Jan 15, 2026 at 12:34 AM CST, Jeff Johnson wrote:
> On 10/30/2025 7:30 AM, Chien Wong wrote:
>
> Subject should have use "ath11k:"
> I'll fix this in my pending branch
>
> And I've removed the ath12k list and added the ath11k list
>
>> Correct a typo in the monitor mode comment where "it make" was mistakenly
>> used instead of "it doesn't make". The comment explains that the brief
>> period where monitor mode appears enabled before being removed is harmless
>> in practice.
>> Also, use more common phrase "in practice" instead of "in practise".
>> 
>> Fixes: 3f6e6c3291ed ("ath11k: disable monitor mode on QCA6390")
>> Fixes: d889913205cf ("wifi: ath12k: driver for Qualcomm Wi-Fi 7 devices")
>
> And I'll drop the Fixes tags since there is no code change and hence no need
> to backport this change to stable kernels.
>

As a newbie in kernel development, I now understand the use of Fixes tag.
Thank you.

Regards,
Chien Wong

  reply	other threads:[~2026-01-15  8:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 14:30 [PATCH] wifi: ath: fix comment typo in monitor mode handling Chien Wong
2026-01-14 16:34 ` Jeff Johnson
2026-01-15  8:20   ` Chien Wong [this message]
2026-01-16  1:26 ` Jeff Johnson

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=DFP0LJ1BX1US.2KD2FIIVAKD3S@xv97.com \
    --to=m@xv97.com \
    --cc=ath11k@lists.infradead.org \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=linux-wireless@vger.kernel.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