aboutsummaryrefslogtreecommitdiff
path: root/Documentation/leds
diff options
context:
space:
mode:
authorStephan Linz2016-06-24 19:16:53 +0200
committerJacek Anaszewski2016-06-27 08:58:35 +0200
commit86ab168614f7ddce0800456ab6da2cf40286a5b2 (patch)
tree11331805ea859d6b1a8ee5a6cc347fd0cefce5be /Documentation/leds
parenteb25cb9956cc9384b7fa0d75dec908c9fac8c444 (diff)
leds: documentation: 'ide-disk' to 'disk-activity'
Signed-off-by: Stephan Linz <linz@li-pro.net> Cc: Joseph Jezak <josejx@gentoo.org> Cc: Jörg Sommer <joerg@alea.gnuu.de> Acked-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
Diffstat (limited to 'Documentation/leds')
-rw-r--r--Documentation/leds/leds-class.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/leds/leds-class.txt b/Documentation/leds/leds-class.txt
index 44f5e6bccd97..f1f7ec9f5cc5 100644
--- a/Documentation/leds/leds-class.txt
+++ b/Documentation/leds/leds-class.txt
@@ -11,7 +11,7 @@ brightness support so will just be turned on for non-zero brightness settings.
The class also introduces the optional concept of an LED trigger. A trigger
is a kernel based source of led events. Triggers can either be simple or
complex. A simple trigger isn't configurable and is designed to slot into
-existing subsystems with minimal additional code. Examples are the ide-disk,
+existing subsystems with minimal additional code. Examples are the disk-activity,
nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
optimises away.