On Tue, Apr 22, 2014 at 8:37 AM, Sander Eikelenboom <linux@xxxxxxxxxxxxxx> wrote: > > Tuesday, April 22, 2014, 5:18:19 PM, you wrote: > >> Applied, I hope it won't blow up again :) > >> johannes > > At least there is some time left this time around ;-) > Will retest tomorrow to at least verify that it indeed also fixes something ! FWIW you had already tested the second patch which had solved your issue, the first patch is an enhancement fix that addresses two regressions introduced by enabling reprocessing of the last request which as Arik found was caused by treating free'ing a new request (or reprocessing after my patch) being processed as a last request. One aspect of the full series I had originally sent out is still not merged and that is the last patch which added opportunistic triggers to check the regulatory queue after bootup. That was rejected based on an architectural design to compartmentalize regulatory and while I could argue with it, over time I think Johannes is right and will send out a follow up patch with a timer for it eventually. The other triggers for hitting the queue can be manual (userspace iw reg set) or beacon hints on 5 GHz channels (most folks will have this) my goal was to automate something to kick it after boot up. 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
