On Fri, 01 Aug 2008, John W. Linville wrote: > On Tue, Jul 22, 2008 at 10:04:00PM -0300, 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? > > > > 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 > > FYI...because you included RFC in the subject I won't be merging > these until I hear otherwise from you. That's fine, they are not for merging yet :-) I have modified some of them a lot, added others, and have not found a good way to do the last one (rate-limiting) properly yet. I will post another "RFC" batch sooner or later, probably during the weekend. This is all 2.6.28 material anyway, so there is no hurry to merge early on wireless-testing, it is best to merge right. If I find anything that looks like a somewhat urgent fix, I will post it separately for merging in 2.6.27. When some of them patch are finally good for merging, I will send a stack just with those and ask for a merge explicitly. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
