From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Pedersen <thomas@cozybit.com>
Cc: linux-wireless@vger.kernel.org, devel@lists.open80211s.org,
linville@tuxdriver.com
Subject: Re: [PATCH 2/2] mac80211: don't transmit 40MHz frames to 20MHz peer
Date: Thu, 03 May 2012 20:55:05 +0200 [thread overview]
Message-ID: <1336071305.5167.5.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1335477667-1625-2-git-send-email-thomas@cozybit.com> (sfid-20120427_000151_701205_D5FEC418)
On Thu, 2012-04-26 at 15:01 -0700, Thomas Pedersen wrote:
> If a mesh peer indicates it is operating as 20MHz-only in its HT
> operation IE, have the rate control algorithm respect this by disabling
> the equivalent bit in the ieee80211_sta HT capabilities.
>
> Signed-off-by: Thomas Pedersen <thomas@cozybit.com>
> ---
> net/mac80211/mesh_plink.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/net/mac80211/mesh_plink.c b/net/mac80211/mesh_plink.c
> index f4124d7..6209327 100644
> --- a/net/mac80211/mesh_plink.c
> +++ b/net/mac80211/mesh_plink.c
> @@ -302,6 +302,12 @@ static struct sta_info *mesh_peer_init(struct ieee80211_sub_if_data *sdata,
> else
> memset(&sta->sta.ht_cap, 0, sizeof(sta->sta.ht_cap));
>
> + if (elems->ht_operation)
> + if (!(elems->ht_operation->ht_param &
> + IEEE80211_HT_PARAM_CHAN_WIDTH_ANY))
> + sta->sta.ht_cap.cap &=
> + ~IEEE80211_HT_CAP_SUP_WIDTH_20_40;
The double if is a bit odd, why not use && to clean up all the
formatting?
johannes
next prev parent reply other threads:[~2012-05-03 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 22:01 [PATCH 1/2] mac80211: insert mesh peer after init Thomas Pedersen
2012-04-26 22:01 ` [PATCH 2/2] mac80211: don't transmit 40MHz frames to 20MHz peer Thomas Pedersen
2012-05-03 18:55 ` Johannes Berg [this message]
2012-05-03 19:02 ` Thomas Pedersen
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=1336071305.5167.5.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=devel@lists.open80211s.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=thomas@cozybit.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).