On Tue, Feb 18, 2014 at 5:24 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxxxxx> wrote: > On Tue, Jan 7, 2014 at 7:35 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: >> On Thu, 2013-12-19 at 12:53 -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. >> >> I don't like this. Can't we just have a self-contained timeout on the >> userspace request instead? > > Sure I'll add this and send a v2 series. Come to think of it -- I am not a fan of the timer. What time do we set for it? What is reasonable? This is what made me instead want to use the notifier hooks. You shouldn't be able to bring up an interface without firmware so hence the hook there, the other one upon register was just another opportunistic one. Please consider this and if you still think a timer is best let me know what the timer value should be :D Luis -- 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
