public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Alejandro Colomar <alx@kernel.org>, linux-wireless@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>,
	Rajkumar Manoharan <rmanohar@qti.qualcomm.com>,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH v1] wifi: ath9k: Fix typo
Date: Mon, 23 Feb 2026 16:17:20 +0100	[thread overview]
Message-ID: <871pibo5fj.fsf@toke.dk> (raw)
In-Reply-To: <6ab107cf786f9d05dc4d84ea4e2d1b219ce108c0.1766355822.git.alx@kernel.org>

Alejandro Colomar <alx@kernel.org> writes:

> This only worked by chance, because all callers of this macro used the
> same identifiers that were expected by the macro.
>
> 	$ grep -rn ath_for_each_chanctx
> 	drivers/net/wireless/ath/ath9k/main.c:1576:	ath_for_each_chanctx(sc, ctx)
> 	drivers/net/wireless/ath/ath9k/main.c:2554:	ath_for_each_chanctx(sc, ctx) {
> 	drivers/net/wireless/ath/ath9k/channel.c:165:	ath_for_each_chanctx(sc, ctx) {
> 	drivers/net/wireless/ath/ath9k/channel.c:291:	ath_for_each_chanctx(sc, ctx) {
> 	drivers/net/wireless/ath/ath9k/channel.c:861:	ath_for_each_chanctx(sc, ctx) {
> 	drivers/net/wireless/ath/ath9k/debug.c:717:	ath_for_each_chanctx(sc, ctx) {
> 	drivers/net/wireless/ath/ath9k/ath9k.h:446:#define ath_for_each_chanctx(_sc, _ctx)                               \
>
> Fixes: c4dc0d040e35 (2014-06-19; "ath9k: Fetch appropriate operating channel context")
> Cc: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
> Cc: John W. Linville <linville@tuxdriver.com>
> Cc: Toke Høiland-Jørgensen <toke@toke.dk>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>

Yeah, looks reasonable - thanks!

Acked-by: Toke Høiland-Jørgensen <toke@toke.dk>

  reply	other threads:[~2026-02-23 15:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-21 22:25 [PATCH v1] wifi: ath9k: Fix typo Alejandro Colomar
2026-02-23 15:17 ` Toke Høiland-Jørgensen [this message]
2026-02-24 18:45   ` Jeff Johnson
2026-02-24 21:27     ` Alejandro Colomar
2026-02-24 21:34       ` Jeff Johnson
2026-02-24 22:55         ` Alejandro Colomar
2026-02-24 23:07           ` Jeff Johnson
2026-02-24 23:09             ` Jeff Johnson
2026-02-24 23:23               ` Alejandro Colomar
2026-02-25  0:04                 ` Jeff Johnson
2026-02-25  0:10                   ` Alejandro Colomar
2026-02-24 21:37       ` Greg KH
2026-02-24 22:52         ` Alejandro Colomar
2026-02-26 21:29 ` 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=871pibo5fj.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=alx@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rmanohar@qti.qualcomm.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