On Wednesday 23 July 2008, Henrique de Moraes Holschuh wrote: > > This is my next batch of rfkill changes. They add features and address > some shortcomings of rfkill-input, mostly. > > Please comment. One thing that is bothering me in the last patch is > what happens during suspend/resume to pending delayed rfkill state > changes. Are pending scheduled jobs executed, cancelled, or frozen to > fire up when the system resumes itself? When using the kernel workqueue, I *think* they are frozen until the system resumes. When using a private workqueue you should use the freezable workqueue allocation. But in this case you are using the kernel workqueue, so I assume it is scheduled untill after resume. > Henrique de Moraes Holschuh (6): > rfkill: detect bogus double-registering > rfkill: add default global states > rfkill: add master_switch_mode functionality > rfkill: add EPO lock to rfkill-input > rfkill: rename rfkill_mutex to rfkill_global_mutex > rfkill: rate-limit rfkill-input workqueue usage > Ivo -- 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
