Hi All, As first discussed here: https://lore.kernel.org/linux-leds/20240601195528.48308-1-hdegoede@xxxxxxxxxx/ Shortly after ledtrig-input-events being merged into leds-for-next I found a serious locking issue with it :| The single patch in this series fixes this. As indicated in the subject this is close to a full rewrite of ledtrig-input-events. The core functionality is preserved and since ledtrig-input-events ATM only exists on leds-for-next the other behavioral changes involved are not a problem. Lee, I personally think it makes sense to keep the history and apply this on top (1). But if you prefer you could also drop the current version and then I'll send out a new patch directly adding the new version of the input-events trigger. Regards, Hans 1) Especially in the light of the similar issues in the netdev trigger Hans de Goede (1): leds: trigger: input-events: Rewrite to fix a serious locking issue drivers/leds/trigger/ledtrig-input-events.c | 136 +++++--------------- 1 file changed, 34 insertions(+), 102 deletions(-) -- 2.45.1
