From: Johannes Berg <johannes@sipsolutions.net>
To: John Crispin <john@phrozen.org>
Cc: linux-wireless@vger.kernel.org, Aloka Dixit <alokad@codeaurora.org>
Subject: Re: [PATCH V5 1/4] nl80211: add basic multiple bssid support
Date: Fri, 06 Nov 2020 10:26:57 +0100 [thread overview]
Message-ID: <504b253121f6edd6e3f48072580af3e15c0bc580.camel@sipsolutions.net> (raw)
In-Reply-To: <aea6777ee2f588cf8df26c416ec0cdb2399ff8cf.camel@sipsolutions.net> (sfid-20201106_102443_717492_2C4D7676)
On Fri, 2020-11-06 at 10:24 +0100, Johannes Berg wrote:
>
> and get rid of NL80211_MULTIPLE_BSSID_IES_MAX.
Oh, and the fact that this today has a value of 8 _probably_ means you
hardcoded the limits of your specific device that you were thinking of
now, and we really should have the device advertising the maximum
possible value or so?
And then I guess we can still hard-code the maximum possible value in
cfg80211.h somewhere, use it for array sizes etc., but limit the
userspace API to the driver-advertised value (and check in wiphy
registration that the cfg80211 limit is >= the driver value).
Or is this some fundamental (spec) limit?
johannes
next prev parent reply other threads:[~2020-11-06 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 9:17 [PATCH V5 0/4] mac80211: add multiple bssid support John Crispin
2020-11-03 9:17 ` [PATCH V5 1/4] nl80211: add basic " John Crispin
2020-11-06 9:24 ` Johannes Berg
2020-11-06 9:26 ` Johannes Berg [this message]
2020-11-03 9:17 ` [PATCH V5 2/4] mac80211: add multiple bssid support to interface handling John Crispin
2020-11-03 9:17 ` [PATCH V5 3/4] mac80211: add multiple bssid/EMA support to beacon handling John Crispin
2020-11-06 9:31 ` Johannes Berg
2020-11-03 9:17 ` [PATCH V5 4/4] mac80211: don't allow CSA on non-transmitting interfaces John Crispin
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=504b253121f6edd6e3f48072580af3e15c0bc580.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=alokad@codeaurora.org \
--cc=john@phrozen.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox