On Wed, Sep 01, 2010 at 06:04:35PM +0200, Johannes Berg wrote: > > Cancel at the end of iwl_cancel_scan_deferred_work() is for case > > when we still get notification from f/w and clear STATUS_SCAN_HW bit in > > iwl_rx_scan_complete_notif. This can happen when firmware is in some > > sane state but we do restart (for example: when debugfs force_reset > > file was used). > > > > For the same reason we need have to iwl_bg_scan_completed allow to run > > in parallel with iwl_bg_restart. To complete scanning when performing > > restart, but f/w is responsible. > > I think you mean "responsive"? Otherwise what you're saying doesn't make > much sense to me? Ehh, yes responsive. > But they all take the mutex, so they can't run in parallel anyway. So it > only becomes an ordering issue, no? Mutex is not taken all the time in iwl_bg_restart. Stanislaw -- 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
