From: Thomas Pedersen <thomas@noack.us>
To: "Nishikawa, Kenzoh" <Kenzoh.Nishikawa@jp.sony.com>,
devel@lists.open80211s.org,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: Send peering open frame again if beacon from listen state peer is received
Date: Thu, 13 Nov 2014 10:17:58 -0800 [thread overview]
Message-ID: <5464F5D6.5090905@noack.us> (raw)
In-Reply-To: <2EB4F5C65A3B8E4E92660930F4EF6B5B0619B9@JPYOKXMS113.jp.sony.com>
Hi Kenzoh,
Looks like your email is part HTML. Please submit using git-send-email.
Your patch looks ok, just a small comment below.
On 11/12/2014 08:27 PM, Nishikawa, Kenzoh via Devel wrote:
> net/mac80211/mesh_plink.c | 6 ++++++
> 1 file changed, 6 insertions(+)
> diff --git a/net/mac80211/mesh_plink.c b/net/mac80211/mesh_plink.c
> index 32c7bd0..5ca4306 100644
> --- a/net/mac80211/mesh_plink.c
> +++ b/net/mac80211/mesh_plink.c
>
> @@ -524,6 +524,12 @@ void mesh_neighbour_update(struct ieee80211_sub_if_data *sdata,
> sdata->u.mesh.mshcfg.auto_open_plinks &&
> rssi_threshold_check(sta, sdata))
> changed = mesh_plink_open(sta);
> + else if (sta->plink_state == NL80211_PLINK_LISTEN &&
You should probably check for (sdata->u.mesh.security & IEEE80211_MESH_SEC_AUTHED)
as well like in mesh_sta_info_alloc().
> + sdata->u.mesh.user_mpm)
> + cfg80211_notify_new_peer_candidate(sdata->dev, hw_addr,
> + elems->ie_start,
> + elems->total_len,
> + GFP_KERNEL);
> ieee80211_mps_frame_release(sta, elems);
> out:
--
thomas
parent reply other threads:[~2014-11-13 18:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2EB4F5C65A3B8E4E92660930F4EF6B5B0619B9@JPYOKXMS113.jp.sony.com>]
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=5464F5D6.5090905@noack.us \
--to=thomas@noack.us \
--cc=Kenzoh.Nishikawa@jp.sony.com \
--cc=devel@lists.open80211s.org \
--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).