On Tue, 2014-12-16 at 01:41 +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
Applied, but please try to send patches with line-broken commit messages. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
