From: Johannes Berg <johannes@sipsolutions.net>
To: John Crispin <john@phrozen.org>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [PATCH V2 01/10] nl80211: add basic multiple bssid support
Date: Thu, 30 Jul 2020 14:57:41 +0200 [thread overview]
Message-ID: <0a6461103e5b32503e38b5f0d34a4d2c7f4a990d.camel@sipsolutions.net> (raw)
In-Reply-To: <20200706115219.663650-1-john@phrozen.org>
On Mon, 2020-07-06 at 13:52 +0200, John Crispin wrote:
> /**
> @@ -5109,6 +5111,9 @@ struct cfg80211_cqm_config;
> * @pmsr_free_wk: (private) peer measurements cleanup work
> * @unprot_beacon_reported: (private) timestamp of last
> * unprotected beacon report
> + * @multi_bssid_mode: Is this a legacy, transmitted or non-transmitted bssid
> + * @multi_bssid_parent: a non-transmitted bssid has a transmitted parent
> + * @multi_bssid_list: linked list for tracking parent - child relations.
> */
> struct wireless_dev {
> struct wiphy *wiphy;
> @@ -5188,6 +5193,10 @@ struct wireless_dev {
> struct work_struct pmsr_free_wk;
>
> unsigned long unprot_beacon_reported;
> +
> + enum nl80211_multi_bssid_mode multi_bssid_mode;
> + struct wireless_dev *multi_bssid_parent;
> + struct list_head multi_bssid_list;
Ah, I forgot - this was where I thought it'd be better to change ...
after reading the later patches.
Or let me just ask: why is that here? You're passing it down in the
params (code I removed above), and then you're effectively making it the
driver's (mac80211's) responsibility to track it.
So why should it be here? cfg80211 isn't really using this much. I saw
there's a small validation thing here, but that could also be pushed
down, and then this can live in mac80211?
Or do you have any future plans for using this in cfg80211?
johannes
next prev parent reply other threads:[~2020-07-30 12:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 11:52 [PATCH V2 01/10] nl80211: add basic multiple bssid support John Crispin
2020-07-06 11:52 ` [PATCH V2 02/10] nl80211: add attributes for multiple bssid related settings John Crispin
2020-07-30 12:57 ` Johannes Berg
2020-07-06 11:52 ` [PATCH V2 03/10] mac80211: add multiple bssid support John Crispin
2020-07-30 13:03 ` Johannes Berg
2020-07-06 11:52 ` [PATCH V2 04/10] mac80211: add multiple bssid IE parsing John Crispin
2020-07-30 13:05 ` Johannes Berg
2020-07-06 11:52 ` [PATCH V2 05/10] mac80211: propagate multi bssid settings when starting John Crispin
2020-07-30 13:06 ` Johannes Berg
2020-07-06 11:52 ` [PATCH V2 06/10] ath11k: pass multiple bssid info to FW when a new vdev is created John Crispin
2020-08-02 15:02 ` Shay Bar
2020-08-02 15:40 ` John Crispin
2020-07-06 11:52 ` [PATCH V2 07/10] ath11k: add a struct to pass parameters into ath11k_wmi_vdev_up John Crispin
2020-07-06 11:52 ` [PATCH V2 08/10] ath11k: add the multiple bssid IE offset to the beacon template John Crispin
2020-07-06 11:52 ` [PATCH V2 09/10] ath11k: set beacon tx mode John Crispin
2020-07-06 11:52 ` [PATCH V2 10/10] ath11k: set the multiple bssid hw cap John Crispin
2020-07-30 12:55 ` [PATCH V2 01/10] nl80211: add basic multiple bssid support Johannes Berg
2020-07-30 12:57 ` Johannes Berg [this message]
2020-07-30 14:37 ` 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=0a6461103e5b32503e38b5f0d34a4d2c7f4a990d.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath11k@lists.infradead.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