On Wed, Oct 13, 2010 at 03:39:53PM +0200, Stanislaw Gruszka wrote: > Almost anywhere in the code we avoid committing rxon while performing > scan, and make rxon commit when scan complete. Some current patches do > not follow that rule. We have that problem at least in > iwlagn_confirue_filter(), iwl_update_chain_flags() and > iwl_bg_bt_full_concurrency(). Any comments about iwl_update_chain_flags, iwl_bg_bt_full_concurrency ? I would like to know how to deal with them, should we deffer commit_rxon to scan complete, or cancel the scan. Or maybe this is no problem at all, because in example committing rxon vs scan was problem of older firmware? 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
