> + Slightly changed the scanning state machine: The scan > worker is scheduled from the scan response handler, and > we're checking for scan_channel to know if a scan is > currently running. Can you tell my why you change the scanning state machine? What was broken with it, or why is it now better? Also, previously priv->scan_req was the marker that a scan was going on. What did it "buy" to you to change this to priv->scan_channel? -- 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
