diff options
| author | Johannes Berg <johannes.berg@intel.com> | 2016-12-19 11:51:11 +0300 |
|---|---|---|
| committer | Johannes Berg <johannes.berg@intel.com> | 2016-12-20 10:45:54 +0300 |
| commit | 7b854982b273134e4ff02c61a74e70e1b1876286 (patch) | |
| tree | b0c7319696809d511230ec31b9ef20af5c7ff610 /crypto/lz4.c | |
| parent | e77a8be9a0a7f2c10151967e3c72c5afcbd41117 (diff) | |
| download | linux-7b854982b273134e4ff02c61a74e70e1b1876286.tar.xz | |
Revert "rfkill: Add rfkill-any LED trigger"
This reverts commit 73f4f76a196d7adb11a1e192bd8024fe0bc83910.
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>
Diffstat (limited to 'crypto/lz4.c')
0 files changed, 0 insertions, 0 deletions