From: Alex Gavin <alex.gavin@candelatech.com>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>,
nbd@nbd.name, lorenzo@kernel.org
Cc: linux-wireless@vger.kernel.org, ryder.lee@mediatek.com,
shayne.chen@mediatek.com
Subject: Re: [PATCH v2] wifi: mt76: mt7996: remove beacon_int_min_gcd from ADHOC interface combinations
Date: Mon, 20 Jul 2026 09:25:35 -0700 [thread overview]
Message-ID: <a6c1fe34-bfe1-4a5f-906f-0959a86e37d4@candelatech.com> (raw)
In-Reply-To: <407f7ac5-0e97-4c84-8272-c0f3cec3890c@candelatech.com>
On 7/20/26 09:17, Alex Gavin wrote:
> On 7/19/26 23:04, Jose Ignacio Tornos Martinez wrote:
>> Hi Felix, Lorenzo,
>>
>> Just a gentle ping on this patch when you have a chance to take a look.
>>
>> It fixes a device registration failure (-EINVAL) for mt7996/mt7992
>> devices
>> introduced by commit 5ef0e8e2653b. Without this fix the device is
>> completely
>> unusable, as cfg80211 validates all advertised interface combinations at
>> registration time and rejects the entire driver.
>>
>> Please let me know if there is anything I should improve or change.
>>
>> Thank you for your time
>>
>> Best regards,
>> Jose Ignacio
>>
>
> This patch fixes driver initialization in my testing. I had previously
> used this patch [1] from OpenWRT's tree as a workaround. I have not done
> any testing with IBSS/ADHOC interfaces, though.
>
>
> Best,
>
> Alex
>
> [1] https://github.com/openwrt/openwrt/blob/main/package/kernel/
> mac80211/patches/subsys/220-allow-ibss-mixed.patch
>
Tested-by: Alex Gavin <alex.gavin@candelatech.com>
prev parent reply other threads:[~2026-07-20 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 10:43 [PATCH v2] wifi: mt76: mt7996: remove beacon_int_min_gcd from ADHOC interface combinations Jose Ignacio Tornos Martinez
2026-07-20 6:04 ` Jose Ignacio Tornos Martinez
2026-07-20 16:17 ` Alex Gavin
2026-07-20 16:25 ` Alex Gavin [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=a6c1fe34-bfe1-4a5f-906f-0959a86e37d4@candelatech.com \
--to=alex.gavin@candelatech.com \
--cc=jtornosm@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=shayne.chen@mediatek.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