From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Gokul Sivakumar <gokulkumar.sivakumar@infineon.com>
Cc: linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
wlan-kernel-dev-list@infineon.com
Subject: Re: [PATCH] brcmfmac: support AP isolation to restrict reachability between stations
Date: Thu, 24 Apr 2025 13:36:09 +0200 [thread overview]
Message-ID: <2a6f7d20-2901-46d6-a16a-b977ff0a3724@broadcom.com> (raw)
In-Reply-To: <9e6febe76a55053972049b13b254474a82b26571.camel@sipsolutions.net>
On 4/24/2025 12:22 PM, Johannes Berg wrote:
> On Thu, 2025-04-24 at 11:50 +0200, Arend van Spriel wrote:
>>
>> Looked at other drivers implementing this callback and here are the results:
>>
>> [wil6210] wil_cfg80211_change_bss(): does exactly the same thing.
>> [wilc1000] change_bss(): worse! it accepts everything and does nothing.
>> [rtl8723bs] cfg80211_rtw_change_bss(): same. just an empty callback.
>
> OK, though I guess other drivers being bad doesn't mean this one should
> be :)
Sure. I am on your team in this. Can you recommend a plan of attack
here? Should we add a mechanism to expose what BSS parameter changes the
driver can handle similar to what is used for struct
station_info::bss_params?
>> If this patch means Infineon is (mildly) regaining interest in upstream
>> wifi development let's not discourage them.
>
> Fair. I didn't mean to discourage. I just think to meaningfully
> contribute upstream people should follow the list. And even review other
> people's patches. I've been meaning to make that more of a requirement,
> since I can't possibly meaningfully review everything I now need to
> merge.
>
> https://lore.kernel.org/linux-wireless/21896d2788b8bc6c7fcb534cd43e75671a57f494.camel@sipsolutions.net/
Yeah. It's a bit of a tough spot I reckon.
>> I do watch the
>> linux-wireless list on occasion but I am a bit lost on your remark. What
>> do you mean by tree tags. You mean the "wifi:" prefix? But then I am
>> confused about the "subject prefix" remark.
>
> Oh, well I guess terminology:
Ack.
Regards,
Arend
next prev parent reply other threads:[~2025-04-24 11:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 17:51 [PATCH] brcmfmac: support AP isolation to restrict reachability between stations Gokul Sivakumar
2025-04-23 22:15 ` Johannes Berg
2025-04-24 9:50 ` Arend van Spriel
2025-04-24 10:22 ` Johannes Berg
2025-04-24 11:36 ` Arend van Spriel [this message]
2025-04-24 11:46 ` Johannes Berg
2025-04-24 12:16 ` Arend van Spriel
2025-04-26 7:51 ` Gokul Sivakumar
2025-04-26 8:37 ` Johannes Berg
2025-04-29 8:22 ` Arend van Spriel
2025-04-30 9:56 ` Johannes Berg
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=2a6f7d20-2901-46d6-a16a-b977ff0a3724@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=gokulkumar.sivakumar@infineon.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=wlan-kernel-dev-list@infineon.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