On Mon, 2016-02-22 at 11:36 -0500, João Paulo Rechi Vita wrote: > This series implements an airplane-mode indicator LED trigger, which > can be > used by platform drivers. The default policy have have airplane-mode > set when > all the radios known by RFKill are OFF, and unset otherwise. This > policy can be > overwritten by one single userspace application at a time using the > operations > _AIRPLANE_MODE_INDICATOR_ACQUIRE and _AIRPLANE_MODE_INDICATOR_CHANGE. > Double-check your commit messages on some of these patches; they didn't get updated to add INDICATOR. Dan > When the > airplane-mode indicator state changes, userspace gets notifications > through the > RFKill control misc device (/dev/rfkill). > > The series also contains a few general fixes and improvements to the > subsystem. > > Additionally, I have a couple of patches to have this feature > supported by the > userspace tool 'rfkill' [1]. Should I use a different subject prefix > to help > separate those from kernel patches in linux-wireless? > > [1] https://wireless.wiki.kernel.org/en/users/documentation/rfkill > > João Paulo Rechi Vita (10): > rfkill: Improve documentation language > rfkill: Remove extra blank line > rfkill: Point to the correct deprecated doc location > rfkill: Move "state" sysfs file back to stable > rfkill: Factor rfkill_global_states[].cur assignments > rfkill: Add documentation about LED triggers > rfkill: Create "rfkill-airplane-mode" LED trigger > rfkill: Use switch to demux userspace operations > rfkill: Userspace control for airplane mode > rfkill: Notify userspace of airplane-mode state changes > > Documentation/ABI/obsolete/sysfs-class-rfkill | 20 ---- > Documentation/ABI/stable/sysfs-class-rfkill | 27 ++++- > Documentation/rfkill.txt | 17 +++ > include/uapi/linux/rfkill.h | 6 + > net/rfkill/core.c | 162 > ++++++++++++++++++++------ > 5 files changed, 173 insertions(+), 59 deletions(-) > delete mode 100644 Documentation/ABI/obsolete/sysfs-class-rfkill > -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
