On Mon, 2016-02-15 at 14:35 +0100, Arend van Spriel wrote: > When user-space has started a critical protocol session and a > disconnect > event occurs, the rdev::crit_prot_nlportid remains set. This caused a > subsequent NL80211_CMD_CRIT_PROTO_START to fail (-EBUSY). Fix this by > clearing the rdev attribute and call .crit_proto_stop() callback upon > disconnect event. > Applied. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
