linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Ashok Nagarajan <ashok@cozybit.com>
Cc: linux-wireless@vger.kernel.org, johannes@sipsolutions.net,
	javier@cozybit.com, devel@lists.open80211s.org
Subject: Re: [PATCH 3/4] mac80211: Allow nonHT/HT peering in mesh
Date: Mon, 30 Apr 2012 15:09:35 -0400	[thread overview]
Message-ID: <20120430190935.GF2560@tuxdriver.com> (raw)
In-Reply-To: <1335498506-9600-3-git-send-email-ashok@cozybit.com>

On Thu, Apr 26, 2012 at 08:48:25PM -0700, Ashok Nagarajan wrote:
> Now that we have protection enabled, allow non-HT and HT20 stations to peer
> with HT40+/- stations. Peering is still disallowed for HT40+/- mismatch.
> 
> Signed-off-by: Ashok Nagarajan <ashok@cozybit.com>
> Reviewed-by: Thomas Pedersen <thomas@cozybit.com>

  CC      net/mac80211/mesh.o
net/mac80211/mesh.c: In function ‘mesh_matches_local’:
net/mac80211/mesh.c:79:28: warning: ‘sta_channel_type’ may be used uninitialized in this function

Please don't add warnings!

> ---
>  net/mac80211/mesh.c |   12 +++++++++---
>  1 files changed, 9 insertions(+), 3 deletions(-)
> 
> diff --git a/net/mac80211/mesh.c b/net/mac80211/mesh.c
> index 8a952e0..d25cb78 100644
> --- a/net/mac80211/mesh.c
> +++ b/net/mac80211/mesh.c
> @@ -76,6 +76,7 @@ bool mesh_matches_local(struct ieee80211_sub_if_data *sdata,
>  	struct ieee80211_if_mesh *ifmsh = &sdata->u.mesh;
>  	struct ieee80211_local *local = sdata->local;
>  	u32 basic_rates = 0;
> +	enum nl80211_channel_type sta_channel_type;
>  
>  	/*
>  	 * As support for each feature is added, check for matching
> @@ -102,10 +103,15 @@ bool mesh_matches_local(struct ieee80211_sub_if_data *sdata,
>  	if (sdata->vif.bss_conf.basic_rates != basic_rates)
>  		goto mismatch;
>  
> -	/* disallow peering with mismatched channel types for now */
> +	if (ie->ht_operation)
> +		sta_channel_type =
> +			ieee80211_ht_oper_to_channel_type(ie->ht_operation);
> +
> +	/* Disallow HT40+/- mismatch */
>  	if (ie->ht_operation &&
> -	    (local->_oper_channel_type !=
> -	     ieee80211_ht_oper_to_channel_type(ie->ht_operation)))
> +	    local->_oper_channel_type > NL80211_CHAN_HT20 &&
> +	    sta_channel_type > NL80211_CHAN_HT20 &&
> +	    local->_oper_channel_type != sta_channel_type)
>  		goto mismatch;
>  
>  	return true;
> -- 
> 1.7.5.4
> 
> 

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2012-04-30 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27  3:48 [PATCH 1/4] mac80211: Advertise HT protection mode in IEs Ashok Nagarajan
2012-04-27  3:48 ` [PATCH 2/4] mac80211: Implement HT mixed protection mode Ashok Nagarajan
2012-04-27  3:48 ` [PATCH 3/4] mac80211: Allow nonHT/HT peering in mesh Ashok Nagarajan
2012-04-30 19:09   ` John W. Linville [this message]
2012-04-30 20:46     ` Ashok Nagarajan
2012-04-27  3:48 ` [PATCH 4/4] [nl,cfg,mac]80211: Allow user to see/configure HT protection mode Ashok Nagarajan

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=20120430190935.GF2560@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=ashok@cozybit.com \
    --cc=devel@lists.open80211s.org \
    --cc=javier@cozybit.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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).