From: Karl Mehltretter <kmehltretter@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Karl Mehltretter" <kmehltretter@gmail.com>,
"John Crispin" <john@phrozen.org>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
"Miri Korenblit" <miriam.rachel.korenblit@intel.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] wifi: mac80211: Fix beacon, TXQ and RX OMI kernel-doc references
Date: Sat, 12 Sep 2026 00:53:42 +0200 [thread overview]
Message-ID: <20260911225342.11342-1-kmehltretter@gmail.com> (raw)
Several mac80211 kernel-doc comments misspell the functions they
describe. Refer to ieee80211_beacon_cntdwn_is_complete() for countdown
completion, ieee80211_next_txq() in the transmit queue scheduling
documentation, and ieee80211_prepare_rx_omi_bw() in the receive
bandwidth finalization documentation.
These corrections make the references match the existing APIs.
Fixes: 8552a434b6a0 ("mac80211: rename csa counters to countdown counters")
Fixes: da7f40c05c16 ("wifi: mac80211: add some support for RX OMI power saving")
Fixes: b4809e9484da ("mac80211: Add airtime accounting and scheduling to TXQs")
Assisted-by: LLM
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
include/net/mac80211.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/net/mac80211.h b/include/net/mac80211.h
index 9d1fac6e808298e068bd819897cc7cabee3fc2b8..e8d35f431a1bcb0779fac9aebd6a6f7f4ba9ac2d 100644
--- a/include/net/mac80211.h
+++ b/include/net/mac80211.h
@@ -4594,7 +4594,7 @@ struct ieee80211_prep_tx_info {
* decremented, and when they reach 1 the driver must call
* ieee80211_csa_finish(). Drivers which use ieee80211_beacon_get()
* get the csa counter decremented by mac80211, but must check if it is
- * 1 using ieee80211_beacon_counter_is_complete() after the beacon has been
+ * 1 using ieee80211_beacon_cntdwn_is_complete() after the beacon has been
* transmitted and then call ieee80211_csa_finish().
* If the CSA count starts as zero or 1, this function will not be called,
* since there won't be any time to beacon before the switch anyway.
@@ -7874,7 +7874,7 @@ ieee80211_return_txq(struct ieee80211_hw *hw, struct ieee80211_txq *txq,
* This function is used to check whether given txq is allowed to transmit by
* the airtime scheduler, and can be used by drivers to access the airtime
* fairness accounting without using the scheduling order enforced by
- * next_txq().
+ * ieee80211_next_txq().
*
* Returns %true if the airtime scheduler thinks the TXQ should be allowed to
* transmit, and %false if it should be throttled. This function can also have
@@ -8195,7 +8195,7 @@ bool ieee80211_prepare_rx_omi_bw(struct ieee80211_link_sta *link_sta,
* ieee80211_finalize_rx_omi_bw - finalize BW RX OMI update
* @link_sta: the link STA the OMI was sent to
*
- * See ieee80211_client_prepare_rx_omi_bw(). Context is the same here
+ * See ieee80211_prepare_rx_omi_bw(). Context is the same here
* as well.
*/
void ieee80211_finalize_rx_omi_bw(struct ieee80211_link_sta *link_sta);
--
2.39.5 (Apple Git-154)
reply other threads:[~2026-09-11 22:55 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=20260911225342.11342-1-kmehltretter@gmail.com \
--to=kmehltretter@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=toke@toke.dk \
/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