diff options
author | Johannes Berg <johannes.berg@intel.com> | 2012-11-08 18:31:02 +0100 |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2012-11-26 12:42:58 +0100 |
commit | 42d97a599eb6b2aab3a401b3e5799a399d6c7652 (patch) | |
tree | 1905b71c2092ad299503515dd0d59fa74573cd12 /fs/omfs | |
parent | 028e8da0723a6f6a00d9d1e3dae9ad448a28987e (diff) | |
download | linux-stable-42d97a599eb6b2aab3a401b3e5799a399d6c7652.tar.gz linux-stable-42d97a599eb6b2aab3a401b3e5799a399d6c7652.tar.bz2 linux-stable-42d97a599eb6b2aab3a401b3e5799a399d6c7652.zip |
cfg80211: remove remain-on-channel channel type
As mwifiex (and mac80211 in the software case) are the
only drivers actually implementing remain-on-channel
with channel type, userspace can't be relying on it.
This is the case, as it's used only for P2P operations
right now.
Rather than adding a flag to tell userspace whether or
not it can actually rely on it, simplify all the code
by removing the ability to use different channel types.
Leave only the validation of the attribute, so that if
we extend it again later (with the needed capability
flag), it can't break userspace sending invalid data.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'fs/omfs')
0 files changed, 0 insertions, 0 deletions