| Message ID | 1470192869-4206-1-git-send-email-masashi.honma@gmail.com (mailing list archive) |
|---|---|
| State | Rejected |
| Delegated to: | Johannes Berg |
| Headers | show |
diff --git a/net/mac80211/mesh.c b/net/mac80211/mesh.c index c66411d..ebd4159 100644 --- a/net/mac80211/mesh.c +++ b/net/mac80211/mesh.c @@ -409,10 +409,7 @@ int mesh_add_ht_cap_ie(struct ieee80211_sub_if_data *sdata, u8 *pos; sband = local->hw.wiphy->bands[band]; - if (!sband->ht_cap.ht_supported || - sdata->vif.bss_conf.chandef.width == NL80211_CHAN_WIDTH_20_NOHT || - sdata->vif.bss_conf.chandef.width == NL80211_CHAN_WIDTH_5 || - sdata->vif.bss_conf.chandef.width == NL80211_CHAN_WIDTH_10) + if (!sband->ht_cap.ht_supported) return 0; if (skb_tailroom(skb) < 2 + sizeof(struct ieee80211_ht_cap))
Previously, "HT Capabilities element" was not included in beacon and Mesh Peering Open/Close frames when wpa_supplicant config file includes disable_ht=1 even though HT is capable. But "HT Capabilities element" should not be modified because it is defined by hardware and software spec of the node. We do not change "HT Operation element" code, because it is defined by surrounding environment and configuration of the node. So it could be vanished by disable_ht=1. Signed-off-by: Masashi Honma <masashi.honma@gmail.com> --- net/mac80211/mesh.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-)