From: Masashi Honma <masashi.honma@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Yaniv Machani <yanivma@ti.com>,
linux-kernel@vger.kernel.org, Meirav Kama <meiravk@ti.com>,
"David S. Miller" <davem@davemloft.net>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v3 3/3] mac80211: mesh: fixed HT ies in beacon template
Date: Mon, 1 Aug 2016 21:30:12 +0900 [thread overview]
Message-ID: <75fef3ce-41a6-5845-e9be-d7ff052a07da@gmail.com> (raw)
In-Reply-To: <1470045822.3389.24.camel@sipsolutions.net>
On 2016年08月01日 19:03, Johannes Berg wrote:
>
> But why is that behaviour *correct*? We still support 40 MHz bandwidth
> things, we just don't use them if we disable HT40.
I could not fully understand your concern...
Do you mean we have 2 bugs about disabling HT40 ?
1) bits in HT capabilities IE
2) HT40 still enabled even if it was disabled by wpa_supplicant or
hostapd with disable_ht40
And do you mean 1) and 2) should be fixed at one time ?
Indeed, currently on the view point of opposite peer, HT40 was enabled
even though it was disabled because both 1) and 2) are wrong.
But if only 1) was fixed, this causes unmatch.
Now I do not recognize bug 2).
Do you have any information about 2) ?
next prev parent reply other threads:[~2016-08-01 12:30 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 [this message]
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 ` [PATCH] mac80211: Include HT Capabilities element if capable Masashi Honma
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=75fef3ce-41a6-5845-e9be-d7ff052a07da@gmail.com \
--to=masashi.honma@gmail.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=meiravk@ti.com \
--cc=netdev@vger.kernel.org \
--cc=yanivma@ti.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).