From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [GIT PULL] wireless-2026-04-30
Date: Thu, 30 Apr 2026 07:12:39 -0700 [thread overview]
Message-ID: <20260430071239.36b0e5f0@kernel.org> (raw)
In-Reply-To: <20260430111831.219242-6-johannes@sipsolutions.net>
On Thu, 30 Apr 2026 13:17:52 +0200 Johannes Berg wrote:
> So the LLM floodgates are starting to open ;-) But I'm somewhat
> happy that so far we haven't gotten any really critical reports.
> Here's a couple of first fixes though.
>
> Please pull and let us know if there's any problem.
Looks like this breaks kunit:
ok 70 mac80211-tpe
KTAP version 1
# Subtest: mac80211-mlme-chan-mode
# module: mac80211_tests
1..1
KTAP version 1
# Subtest: test_determine_chan_mode
ok 1 Normal case, EHT is working
ok 2 Requiring EHT support is fine
ok 3 Lowering the mode limits us
kunit: required basic rate or BSS membership selectors not supported or disabled, rejecting connection
ok 4 Requesting a basic rate/selector that we do not support
ok 5 As before, but userspace says it is taking care of it
# test_determine_chan_mode: ASSERTION FAILED at net/mac80211/tests/chan-mode.c:258
Expected conn.mode == params->expected_mode, but
conn.mode == 5 (0x5)
params->expected_mode == 1 (0x1)
not ok 6 Masking out a supported rate in HT capabilities
kunit: Missing mandatory rates for 4 Nss, rx 0, tx 2 oper 2, disable VHT
kunit: required MCSes not supported, disabling VHT
ok 7 Masking out a RX rate in VHT capabilities
kunit: Missing mandatory rates for 4 Nss, rx 2, tx 0 oper 2, disable VHT
kunit: required MCSes not supported, disabling VHT
ok 8 Masking out a TX rate in VHT capabilities
kunit: Missing mandatory rates for 5 Nss, rx 0, tx 0 oper 2, disable VHT
kunit: required MCSes not supported, disabling VHT
ok 9 AP has higher VHT requirement than client
ok 10 all zero VHT basic rates are ignored (many APs broken)
kunit: Invalid rates for 3 Nss, rx 3, tx 3 oper 0, disable HE
kunit: required MCSes not supported, disabling HE
ok 11 AP requires 3 HE streams but client only has two
ok 12 all zero HE basic rates are ignored (iPhone workaround)
kunit: required MCSes not supported, disabling EHT
ok 13 AP requires too many RX streams with EHT MCS 7
kunit: required MCSes not supported, disabling EHT
ok 14 AP requires too many TX streams with EHT MCS 7
kunit: required MCSes not supported, disabling EHT
kunit: required basic rate or BSS membership selectors not supported or disabled, rejecting connection
ok 15 AP requires too many RX streams with EHT MCS 7 and EHT is required
kunit: regulatory prevented using AP config, downgraded
kunit: required bandwidth not supported, disabling EHT
ok 16 80 MHz EHT is downgraded to 40 MHz HE due to puncturing
# test_determine_chan_mode: pass:15 fail:1 skip:0 total:16
not ok 1 test_determine_chan_mode
# Totals: pass:15 fail:1 skip:0 total:16
next prev parent reply other threads:[~2026-04-30 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 11:17 [GIT PULL] wireless-2026-04-30 Johannes Berg
2026-04-30 14:12 ` Jakub Kicinski [this message]
2026-04-30 15:51 ` Johannes Berg
2026-04-30 16:27 ` Jakub Kicinski
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=20260430071239.36b0e5f0@kernel.org \
--to=kuba@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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