On Fri, 2014-11-21 at 09:11 +0000, Nishikawa, Kenzoh wrote: > Instead of sending peer candidate events just once, send them as long as the > peer remains in the LISTEN state in the peering state machine, when userspace > is implementing the peering manager. Userspace may silence the events from a > peer by progressing the state machine or by setting the link state to BLOCKED. > > Fixes the problem that a mesh peering process won't be fired again after the > previous first peering trial fails due to like air propagation error if the > peering is managed by user space such as wpa_supplicant. > > This patch works with another patch for wpa_supplicant described here which > fires a peering process again triggered by the notice from kernel. > http://lists.shmoo.com/pipermail/hostap/2014-November/031235.html
Please break those long lines to <72 characters. > + else if (sta->plink_state == NL80211_PLINK_LISTEN && > + (sdata->u.mesh.user_mpm || > + sdata->u.mesh.security & IEEE80211_MESH_SEC_AUTHED)) the latter two lines should be indented by one more space johannes _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
