[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f9c9bb95-161b-4565-b8d3-fc41c7fe3b29@leemhuis.info>
Date: Fri, 13 Oct 2023 15:21:17 +0200
From: "Linux regression tracking #update (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Oleksandr Natalenko <oleksandr@...alenko.name>,
linux-wireless@...r.kernel.org
Cc: Felix Fietkau <nbd@....name>, Sasha Levin <sashal@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
stable@...r.kernel.org, linux-kernel@...r.kernel.org,
Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: [PATCH 1/3] wifi: mt76: mt7915: remove VHT160 capability on
MT7915
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 22.09.23 13:22, Linux regression tracking #adding (Thorsten Leemhuis)
wrote:
>
> On 21.09.23 07:02, Oleksandr Natalenko wrote:
>> On středa 26. července 2023 11:17:02 CEST Felix Fietkau wrote:
>>> The IEEE80211_VHT_CAP_EXT_NSS_BW value already indicates support for half-NSS
>>> 160 MHz support, so it is wrong to also advertise full 160 MHz support.
> [...]
>> and this broke my mt7915-based AP.
>>
>> However, if I remove `[VT160]` capability from the hostapd config, things go back to normal. It does seem that 160 MHz still works even.
>>
>> Is this expected?
>
> Thanks for the report.
Removing this from the regression tracking after mentioning the intent
to do so due to the tricky striation in my last report to Linus.
#regzbot inconclusive: tricky situation, no simple way out afaics
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
Powered by blists - more mailing lists