On Sun, Feb 06, 2011 at 09:29:45AM -0800, Wey-Yi Guy wrote: > From: Don Fry <donald.h.fry@xxxxxxxxx> > > With commit 554d1d027b19265c4aa3f718b3126d2b86e09a08 only one RF_KILL > interrupt will be seen by the driver when the interface is down. > > Re-enable the interrupt when it occurs to see all transitions. What practical problem this fix? I'm asking, because my RF_KILL commit went to stable, shouldn't this fix go to stable as well? We seeing problem when we perform the following step: 1. Load the driver 2. Switch HW RF kill ON 3. Switch HW RF Kill OFF 4. Check the status with "rfkill list" Repeat few time, the "Hard blocked" will stay "yes", at this point, the only way to fix is to unload the driver. You are right, this patch should back port to stable since the commit 554d1d027b19265c4aa3f718b3126d2b86e09a08 backport to stable. Wey -- 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
