On Tue, 26 Aug 2008, Greg KH wrote: > > Drivers that need rfkill's older behaviour will have to implement it by > > themselves in their own suspend handling. [...] > > The following drivers need to check if they need to explicitly block > > their transmitters in their own suspend handlers (maintainers Cc'd): > > Normally when you change a kernel-api to operate differently, you also > fix up the relevant parts of the kernel as well. Have you looked into That requires one to actually KNOW the details of the relevant parts of the kernel. In this case, the particular needs of several devices and their device drivers. Which I don't, for many of them. > these drivers to see if they do have this problem or not? Those I know enough to be 100% certain that do not need it (or actually REQUIRE it not to happen, like libertas) have not been added to the CC. There were none I could be 100% certain that would need the toggle_radio call (if there were, they would have been fixed by the patch as well). For all the others that I am not sure of, I CC'd the maintainers. If any of them reply indicating that they need the explicit toggle_radio() call, we can add such changes to the patch (or in a future patch). I consider this equivalent to emailing everyone and asking about it. -- "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
