diff options
| author | Florian Eckert <fe@dev.tdt.de> | 2020-02-05 09:20:39 +0100 |
|---|---|---|
| committer | Paul Spooren <mail@aparcar.org> | 2021-03-05 00:10:06 -1000 |
| commit | c24c23e1851ff6c51649d094ae34ff3ba49f64e0 (patch) | |
| tree | 4211352aa846cde722548f6713d1959f996502d5 /target/linux | |
| parent | dec14ac436325abddd0ded06f34e95425fc9a75e (diff) | |
| download | upstream-c24c23e1851ff6c51649d094ae34ff3ba49f64e0.tar.gz upstream-c24c23e1851ff6c51649d094ae34ff3ba49f64e0.tar.bz2 upstream-c24c23e1851ff6c51649d094ae34ff3ba49f64e0.zip | |
rssileds: use new application led trigger backend
This will use the new application led trigger backend. For now this is
the only package that uses leds trigger in user space to configure the
kernel led triggers.
The callback script only emmits a message for now, so that this LED is now
managed by the rssileds service. Until now a generic warning was emitted that
this LED trigger is not supported. But that is not true.
-> Skipping trigger 'rssileds' for led '<name>' due to missing kernel module
I think this callback should be changed in the future to restart the
service.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Diffstat (limited to 'target/linux')
0 files changed, 0 insertions, 0 deletions