On Mon, 03 Nov 2008, Matthew Garrett wrote: > On Mon, Nov 03, 2008 at 01:02:29PM -0200, Henrique de Moraes Holschuh wrote: > > Right now, you should still rfkill_force_state(). Please wait for an hour > > or two while I clean up that broken resume handling, and I will tell you for > > sure. > > Cool. I'll hold off posting my cleanups until then in that case. Ok, two bugs reproduced, the fixes are ready and tested, and I will be sending it now to linux-wireless. You're in the CC, so you will get them. I will also need to send patches for -stable, as the ones for mainline won't apply to -stable. Now, for what you asked: you DO NOT HAVE to use rfkill_force_state() in your driver's resume method, as long as you NEVER make use of RFKILL_STATE_HARD_BLOCKED. I have fixed the bug that was messing this up. -- "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-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
