diff options
| author |   Luis R. Rodriguez <mcgrof@do-not-panic.com> | 2013-11-05 09:18:00 -0800 |
|---|---|---|
| committer |   Johannes Berg <johannes.berg@intel.com> | 2013-11-25 20:49:45 +0100 |
| commit | 222ea5819901ed174db4df2e26aa5e982f857845 (patch) | |
| tree | 1552374c866b454e657ca9978b4ac994e86966dc /net/wireless/reg.c | |
| parent | cfg80211: DFS check chandef usable before CAC (diff) | |
| download | linux-dev-222ea5819901ed174db4df2e26aa5e982f857845.tar.xz linux-dev-222ea5819901ed174db4df2e26aa5e982f857845.zip | |
cfg80211: force WIPHY_FLAG_CUSTOM_REGULATORY on wiphy_apply_custom_regulatory()
wiphy_apply_custom_regulatory() implies WIPHY_FLAG_CUSTOM_REGULATORY
but we never enforced it, do that now and warn if the driver
didn't set it. All drivers should be following this today already.
Having WIPHY_FLAG_CUSTOM_REGULATORY does not however mean you will
use wiphy_apply_custom_regulatory() though, you may have your own
_orig value set up tools / helpers. The intel drivers are examples
of this type of driver.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'net/wireless/reg.c')
| -rw-r--r-- | net/wireless/reg.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/net/wireless/reg.c b/net/wireless/reg.c index e4e3337ba296..04b6fe4b7653 100644 --- a/net/wireless/reg.c +++ b/net/wireless/reg.c @@ -1292,6 +1292,10 @@ void wiphy_apply_custom_regulatory(struct wiphy *wiphy, enum ieee80211_band band; unsigned int bands_set = 0; + WARN(!(wiphy->flags & WIPHY_FLAG_CUSTOM_REGULATORY), + "wiphy should have WIPHY_FLAG_CUSTOM_REGULATORY\n"); + wiphy->flags |= WIPHY_FLAG_CUSTOM_REGULATORY; + for (band = 0; band < IEEE80211_NUM_BANDS; band++) { if (!wiphy->bands[band]) continue; |