Hi Johannes, > Would everybody be happy with this rolled in? > > johannes > > Subject: rfkill: userspace API improvements > > This adds the two following things to /dev/rfkill: > 1) notification to userspace with a new operation > RFKILL_OP_NVS_REPORT about default states restored > from platform non-volatile storage I really don't understand why this is needed. What benefit does it give us compared to just sent OP_CHANGE and OP_CHANGE as an update. My X200 for example does this anyway on suspend/resume. So what is rfkilld suppose to be doing when receiving this report? What is the expected behavior? Why do we bother with multi-OS crap here? I am really unclear what are we trying to solve here. > 2) the ability to ignore input events in the kernel > while a handler daemon is connected, if the input > part is compiled in. For the rfkill-input ioctl: Acked-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> Regards Marcel -- 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
