| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | rssileds: use new application led trigger backend | Florian Eckert | 2021-03-05 | 1 | -0/+3 |
| | | | | | | | | | | | | | | | | | | 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> | ||||
| * | rssileds: change rssileds.init STOP index | Joseph Tingiris | 2019-06-24 | 1 | -1/+1 |
| | | | | | | | | | | This patch is in a series to allow additional STOP indexes after umount, so that other block devices may stop cleanly. rssileds.init is now STOP=89 Signed-off-by: Joseph Tingiris <joseph.tingiris@gmail.com> | ||||
| * | packages: sort network related packages into package/network/ | Felix Fietkau | 2012-10-10 | 1 | -0/+75 |
| SVN-Revision: 33688 | |||||
 |
index : openwrt/upstream | |
| upstream openwrt | James |
| aboutsummaryrefslogtreecommitdiffstats |