On Tue, 2011-12-20 at 14:55 +0200, Eyal Shapira wrote: > stop sched scan isn't an immediate operation > and we need to wait for PERIODIC_SCAN_COMPLETE_EVENT_ID > after sending a stop before changing internal state > and notifying upper layers. > Not doing this caused problems when canceling an existing sched > scan and immediately requesting to start a new one > with a different configuration as the FW was still > in the middle of the previous sched scan. > > Signed-off-by: Eyal Shapira <eyal@xxxxxxxxxx> > --- Applied, thanks! -- Cheers, Luca. -- 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
