On Wed, 2014-02-26 at 12:38 -0800, Luis R. Rodriguez wrote: > This adds a trigger to review any pending regulatory > requests whenever an 802.11 device interface is brought > down or up. We use this as an opportunistic trigger > for checking the regulatory work queues as otherwise > they they're only checked upon an initial regulatory > request or when beacon hints are found. > > This opportunistic mechanism can be used to trigger > kicking the queues regulatory queues at any time from > userspace without having to change the regulatory state. > > A timer just waiting upon init is not that appropriate > as when it should be triggered will depend on systems, > a much better approach is to use and add opportunistic > triggers. The interface coming up is typically a good > indicator that filesystems have been mounted since > firmware is required for some devices. I still don't like it. You have a problem in the regulatory code and work around it by hooking into random parts of the other code - can't you fix it properly in the regulatory code? 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
