Home
last modified time | relevance | path

Searched hist:"97 d910d0" (Results 1 – 4 of 4) sorted by relevance

/openbmc/linux/net/wireless/
H A Dutil.c97d910d0 Thu Jan 15 09:05:21 CST 2015 Johannes Berg <johannes.berg@intel.com> cfg80211: remove 80+80 MHz rate reporting

These rates are treated the same as 160 MHz in the spec, so
it makes no sense to distinguish them. As no driver uses them
yet, this is also not a problem, just remove them.

In the userspace API the field remains reserved to preserve
API and ABI.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>

H A Dnl80211.c97d910d0 Thu Jan 15 09:05:21 CST 2015 Johannes Berg <johannes.berg@intel.com> cfg80211: remove 80+80 MHz rate reporting

These rates are treated the same as 160 MHz in the spec, so
it makes no sense to distinguish them. As no driver uses them
yet, this is also not a problem, just remove them.

In the userspace API the field remains reserved to preserve
API and ABI.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>

/openbmc/linux/include/uapi/linux/
H A Dnl80211.h97d910d0 Thu Jan 15 09:05:21 CST 2015 Johannes Berg <johannes.berg@intel.com> cfg80211: remove 80+80 MHz rate reporting

These rates are treated the same as 160 MHz in the spec, so
it makes no sense to distinguish them. As no driver uses them
yet, this is also not a problem, just remove them.

In the userspace API the field remains reserved to preserve
API and ABI.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
97d910d0 Thu Jan 15 09:05:21 CST 2015 Johannes Berg <johannes.berg@intel.com> cfg80211: remove 80+80 MHz rate reporting

These rates are treated the same as 160 MHz in the spec, so
it makes no sense to distinguish them. As no driver uses them
yet, this is also not a problem, just remove them.

In the userspace API the field remains reserved to preserve
API and ABI.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
/openbmc/linux/include/net/
H A Dcfg80211.h97d910d0 Thu Jan 15 09:05:21 CST 2015 Johannes Berg <johannes.berg@intel.com> cfg80211: remove 80+80 MHz rate reporting

These rates are treated the same as 160 MHz in the spec, so
it makes no sense to distinguish them. As no driver uses them
yet, this is also not a problem, just remove them.

In the userspace API the field remains reserved to preserve
API and ABI.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
97d910d0 Thu Jan 15 09:05:21 CST 2015 Johannes Berg <johannes.berg@intel.com> cfg80211: remove 80+80 MHz rate reporting

These rates are treated the same as 160 MHz in the spec, so
it makes no sense to distinguish them. As no driver uses them
yet, this is also not a problem, just remove them.

In the userspace API the field remains reserved to preserve
API and ABI.

Signed-off-by: Johannes Berg <johannes.berg@intel.com>