On Thu, 2012-11-08 at 14:37 +0200, Arik Nemtsov wrote: > The lower driver might rely on getting zeroed per-vif private memory > when an interface is added. Resetting the memory on removal avoids > adverse affects during recovery, where the interface is added without > being removed. However, it means that data isn't stable across suspend/resume, which could be desirable to the driver as it may want to have the same configuration after resuming. I think we should therefore leave this to the driver, it's obviously easily implemented as the last step of the driver's ->remove_interface() johannes -- 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
