From: Masashi Honma <masashi.honma@gmail.com>
To: johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, j@w1.fi, me@bobcopeland.com,
Masashi Honma <masashi.honma@gmail.com>
Subject: [PATCH] mac80211: Include HT Capabilities element if capable
Date: Wed, 3 Aug 2016 11:54:29 +0900 [thread overview]
Message-ID: <1470192869-4206-1-git-send-email-masashi.honma@gmail.com> (raw)
In-Reply-To: <1470122837.2665.5.camel@sipsolutions.net>
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(-)
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))
--
2.7.4
prev parent reply other threads:[~2016-08-03 3:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 20:07 [PATCH v3 3/3] mac80211: mesh: fixed HT ies in beacon template Yaniv Machani
2016-07-22 5:26 ` Masashi Honma
2016-07-26 3:41 ` Masashi Honma
2016-08-01 10:03 ` Johannes Berg
2016-08-01 12:30 ` Masashi Honma
2016-08-02 2:59 ` Masashi Honma
2016-08-02 7:27 ` Johannes Berg
2016-08-03 2:51 ` Masashi Honma
2016-08-03 6:50 ` Johannes Berg
2016-08-03 2:54 ` Masashi Honma [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1470192869-4206-1-git-send-email-masashi.honma@gmail.com \
--to=masashi.honma@gmail.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).