summaryrefslogtreecommitdiffstats
path: root/Documentation/bad_memory.txt
diff options
context:
space:
mode:
authorKurt Van Dijck <kurt.van.dijck@eia.be>2012-12-18 18:50:57 +0100
committerMarc Kleine-Budde <mkl@pengutronix.de>2013-01-26 16:58:59 +0100
commita1ef7bd9fce8aba8e4701e60208148fb3bc9bdd4 (patch)
tree0b9008a80fdbe8304f1983980996117024ebc96a /Documentation/bad_memory.txt
parentbf03a5379cd3492fbeca42111340581ba9dee0b8 (diff)
downloadblackbird-op-linux-a1ef7bd9fce8aba8e4701e60208148fb3bc9bdd4.tar.gz
blackbird-op-linux-a1ef7bd9fce8aba8e4701e60208148fb3bc9bdd4.zip
can: rename LED trigger name on netdev renames
The LED trigger name for CAN devices is based on the initial CAN device name, but does never change. The LED trigger name is not guaranteed to be unique in case of hotplugging CAN devices. This patch tries to address this problem by modifying the LED trigger name according to the CAN device name when the latter changes. v1 - Kurt Van Dijck v2 - Fabio Baltieri - remove rename blocking if trigger is bound - use led-subsystem function for the actual rename (still WiP) - call init/exit functions from dev.c v3 - Kurt Van Dijck - safe operation for non-candev based devices (vcan, slcan) based on earlier patch v4 - Kurt Van Dijck - trivial patch mistakes fixed Signed-off-by: Kurt Van Dijck <kurt.van.dijck@eia.be> Signed-off-by: Fabio Baltieri <fabio.baltieri@gmail.com> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'Documentation/bad_memory.txt')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud