On Tue, 01 Jul 2008, Adel Gadllah wrote: > The calls to iwl|iwl3945_rfkill_set_hw_state() had to be moved because > rfkill_force_state() cannot be called from an atomic context. Yeah, the joys of mutexes. If this is going to be a severe annoyance to drivers, I don't see why rfkill could not be changed to use some other locking primitive that does work on atomic contexes. But I am not the right person to do it, I am still learning about all the different locking flavours in Linux. -- "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
