> Every time the driver gets a notification from the card that one of its rfkill > lines changed state (polling might be needed on badly designed cards that don't > @@ -422,13 +423,24 @@ of the hardware is unknown), or read-write (where the hardware can be queried > about its current state). > > The rfkill class will call the get_state hook of a device every time it needs > -to know the *real* current state of the hardware. This can happen often. > +to know the *real* current state of the hardware. This can happen often, but > +it does not do any pooling, so it is not enough on hardware that is subject > +to state changes outside of the rfkill subsystem. pooling -> polling With that typo fixed, you can add my: Acked-by: Ivo van Doorn <IvDoorn@xxxxxxxxx> Ivo -- 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
