On Mon, Jul 21, 2008 at 09:18:21PM -0300, Henrique de Moraes Holschuh wrote: > Every time a new input device that is capable of one of the rfkill EV_SW events > (currently only SW_RFKILL_ALL) is connected to rfkill-input, we must check the > states of the input EV_SW switches and take action. Otherwise, we will ignore > the initial switch state. > > We also need to re-check the states of the EV_SW switches after a device that > was under an exclusive grab is released back to us, since we got no input > events from that device while it was grabbed. > > Signed-off-by: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx> > Cc: Ivo van Doorn <IvDoorn@xxxxxxxxx> > Cc: Dmitry Torokhov <dtor@xxxxxxx> CC [M] net/rfkill/rfkill-input.o net/rfkill/rfkill-input.c: In function ‘rfkill_start’: net/rfkill/rfkill-input.c:201: warning: passing argument 2 of ‘constant_test_bit’ from incompatible pointer type net/rfkill/rfkill-input.c:201: warning: passing argument 2 of ‘variable_test_bit’ from incompatible pointer type net/rfkill/rfkill-input.c:202: warning: passing argument 2 of ‘constant_test_bit’ from incompatible pointer type net/rfkill/rfkill-input.c:202: warning: passing argument 2 of ‘variable_test_bit’ from incompatible pointer type net/rfkill/rfkill-input.c:203: warning: passing argument 2 of ‘constant_test_bit’ from incompatible pointer type net/rfkill/rfkill-input.c:203: warning: passing argument 2 of ‘variable_test_bit’ from incompatible pointer type Don't you need an index for those evbit, swbit, and sw arrays? -- John W. Linville linville@xxxxxxxxxxxxx -- 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
