Johannes Berg 7b854982b2 Revert "rfkill: Add rfkill-any LED trigger" ... This reverts commit 73f4f76a19. As Mike reported, and I should've seen in review, we can't call the new LED functions, which acquire the mutex, from places like rfkill_set_sw_state() that are documented to be callable from any context the user likes to use. For Mike's case it led to a deadlock, but other scenarios are possible. Reported-by: Михаил Кринкин <krinkin.m.u@gmail.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>		2016-12-20 08:45:54 +01:00
..
core.c	Revert "rfkill: Add rfkill-any LED trigger"	2016-12-20 08:45:54 +01:00
input.c	rfkill: don't use [delayed_]work_pending()	2012-12-28 13:40:16 -08:00
Kconfig	net: rfkill: gpio: remove rfkill_gpio_platform_data	2016-02-24 09:13:09 +01:00
Makefile
rfkill-gpio.c	net: rfkill: gpio: remove rfkill_gpio_platform_data	2016-02-24 09:13:09 +01:00
rfkill-regulator.c	net: rfkill: drop owner assignment from platform_drivers	2014-10-20 16:21:58 +02:00
rfkill.h