diff options
| author | John Crispin <john@openwrt.org> | 2015-08-17 06:24:47 +0000 |
|---|---|---|
| committer | John Crispin <john@openwrt.org> | 2015-08-17 06:24:47 +0000 |
| commit | 0f155a330ebb3a0b06a08b1b9a5b3b14d127d557 (patch) | |
| tree | e051c2b1f5d9571a4ecca15b8a28a4290078f054 /target/linux/bcm53xx/patches-3.18/901-mtd-bcm47xxpart-workaround-for-Asus-RT-AC87U-asus-pa.patch | |
| parent | 1a392636a5b5694178d5f802efa9c220ff9dbabf (diff) | |
| download | mtk-20170518-0f155a330ebb3a0b06a08b1b9a5b3b14d127d557.zip mtk-20170518-0f155a330ebb3a0b06a08b1b9a5b3b14d127d557.tar.gz mtk-20170518-0f155a330ebb3a0b06a08b1b9a5b3b14d127d557.tar.bz2 | |
ramips: base-files: optimize etc/diag.sh and etc/board.d/01_leds scripts
Instead of using board name provided explicitly as text in LED name, ex.:
[...]
mlwg2)
status_led="mlwg2:blue:system"
[...]
use $board variable, which allows to combine together multiple boards with same color and LED names, ex:
[...]
mlw221|\
mlwg2)
status_led="$board:blue:system"
[...]
The above approach allows to shrink size of code in base-files/etc/board.d/01_leds and base-files/etc/diag.sh scripts dramatically.
One thing to keep in mind here is that we assume to use proper and consistent LED naming scheme ("device:color:led-name").
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
SVN-Revision: 46665
Diffstat (limited to 'target/linux/bcm53xx/patches-3.18/901-mtd-bcm47xxpart-workaround-for-Asus-RT-AC87U-asus-pa.patch')
0 files changed, 0 insertions, 0 deletions