From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wifi: mac80211: queue frames while off-channel
Date: Fri, 4 Sep 2026 09:29:15 +0200 [thread overview]
Message-ID: <20260904072915.GA41290@wp.pl> (raw)
In-Reply-To: <2476da0c8b837dba5750f7a556d9bac2387a9c59.camel@sipsolutions.net>
On Fri, Sep 04, 2026 at 08:56:13AM +0200, Johannes Berg wrote:
> On Thu, 2026-08-20 at 15:12 +0200, Stanislaw Gruszka wrote:
> >
> > The change depends on the iTXQ resumption handling introduced by
> > commit 4444bc2116ae ("wifi: mac80211: Proper mark iTXQs for resumption")
> > and the wake_tx_queue support introduced by
> > commit a790cc3a4fad ("wifi: mac80211: add wake_tx_queue callback to drivers"),
> > so use those in 'Fixes' tag.
>
> That doesn't really make any sense, IMHO.
Going to drop those 'Fixes:' tags and comment. but I don't know
what the tag should be then.
I saw in docs that 'Fixes:' is required for -stable submissions
for net tree, but maybe I could just skip it for mac80211?
> > --- a/net/mac80211/tx.c
> > +++ b/net/mac80211/tx.c
> > @@ -267,20 +267,14 @@ ieee80211_tx_h_dynamic_ps(struct ieee80211_tx_data *tx)
> > }
> >
> > static ieee80211_tx_result debug_noinline
> > -ieee80211_tx_h_check_assoc(struct ieee80211_tx_data *tx)
> > +ieee80211_tx_h_check_offchannel(struct ieee80211_tx_data *tx)
>
> I (vaguely?) had these ordered by execution order, might make sense to
> move around and try to keep that.
Ok, will move.
> > {
> > -
> > struct ieee80211_hdr *hdr = (struct ieee80211_hdr *)tx->skb->data;
> > - struct ieee80211_tx_info *info = IEEE80211_SKB_CB(tx->skb);
> > - bool assoc = false;
> > -
> > - if (unlikely(info->flags & IEEE80211_TX_CTL_INJECTED))
> > - return TX_CONTINUE;
>
>
> Not sure you should remove that, still you want injection to go out?
>
> Not sure injection should even be queued - maybe you do want to send
> while scanning on a random channel? Or maybe not? Maybe someone depends
> on that behaviour? Or maybe not? Kinda hard to say...
I will keep it v2, change indeed could cause regression for someone.
Regards
Stanislaw
prev parent reply other threads:[~2026-09-04 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 13:12 [PATCH] wifi: mac80211: queue frames while off-channel Stanislaw Gruszka
2026-09-04 6:56 ` Johannes Berg
2026-09-04 7:29 ` Stanislaw Gruszka [this message]
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=20260904072915.GA41290@wp.pl \
--to=stf_xl@wp.pl \
--cc=johannes@sipsolutions.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.