On Mon, Aug 30, 2010 at 09:17:59PM +0200, Johannes Berg wrote: > On Mon, 2010-08-30 at 15:14 -0400, John W. Linville wrote: > > This function exists to clean-up after a hardware error or something > > similar. The restart is accomplished using the same infrastructure used > > to resume after a suspend. The suspend path cancels running scans, so > > it seems appropriate to do that here as well. > > > - /* use this reason, __ieee80211_resume will unblock it */ > > + ieee80211_scan_cancel(local); > > + > > + /* use this reason, ieee80211_reconfig will unblock it */ > > Hmm, yes .. but how will this interact with hw scan? You tell me -- I would think that calling ieee80211_restart_hw would effectively abandon all hope of a hardware scan completing. Should the caller call ieee80211_scan_completed(..., 1)? Or should we do that (or equivalent) here too? John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- 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
