diff options
| author | Luis R. Rodriguez <mcgrof@do-not-panic.com> | 2013-11-05 21:18:00 +0400 |
|---|---|---|
| committer | Johannes Berg <johannes.berg@intel.com> | 2013-11-25 23:49:45 +0400 |
| commit | 222ea5819901ed174db4df2e26aa5e982f857845 (patch) | |
| tree | 1552374c866b454e657ca9978b4ac994e86966dc /include/linux/vmalloc.h | |
| parent | fe7c3a1f20a419d86d3f90316d8efc2d04f3f0ed (diff) | |
| download | linux-222ea5819901ed174db4df2e26aa5e982f857845.tar.xz | |
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 'include/linux/vmalloc.h')
0 files changed, 0 insertions, 0 deletions