On Tue, Apr 22, 2014 at 8:22 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Wed, 2014-04-16 at 12:53 +0200, Janusz Dziedzic wrote: >> Track CRDA request and handle timeout when no answer >> from CRDA. This could happen when crda is not available >> yet (not mounted fs), eg. during OS startup and cfg80211 >> built-in to the kernel. >> Before we could stuck when processing last request >> without ability to process current and any further >> regulatory requests. > > Hmm, this doesn't apply now on top of the patches Luis sent. Was this > the patch that was meant alternatively? Sorry I failed to pick this up amongst the threads, this one is a replacement for the my real original 2nd and 3rd patch (2nd in yesterday's series, but I hadn't redone the 3rd patch from the original series) but I rather we treat things linearly and see if we can split this up a bit, as I see this is an evolution of the work from my original 2nd patch. I'll work on this and send out something shortly. 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
