diff options
author | Maciej S. Szmigiero <mail@maciej.szmigiero.name> | 2016-11-16 00:55:57 +0100 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2016-11-16 10:03:52 +0100 |
commit | 31b5929d533f5183972cf57a7844b456ed996f3c (patch) | |
tree | 8513f3edfdfded7d3c72ea88d01766926e48a8d5 /fs/fhandle.c | |
parent | 26ba68d2f81bc33535d0792013dd4f5de55cb986 (diff) | |
download | talos-obmc-linux-31b5929d533f5183972cf57a7844b456ed996f3c.tar.gz talos-obmc-linux-31b5929d533f5183972cf57a7844b456ed996f3c.zip |
vt: fix Scroll Lock LED trigger name
There is a disagreement between drivers/tty/vt/keyboard.c and
drivers/input/input-leds.c with regard to what is a Scroll Lock LED
trigger name: input calls it "kbd-scrolllock", but vt calls it
"kbd-scrollock" (two l's).
This prevents Scroll Lock LED trigger from binding to this LED by default.
Since it is a scroLL Lock LED, this interface was introduced only about a
year ago and in an Internet search people seem to reference this trigger
only to set it to this LED let's simply rename it to "kbd-scrolllock".
Also, it looks like this was supposed to be changed before this code was
merged: https://lkml.org/lkml/2015/6/9/697 but it was done only on
the input side.
Signed-off-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>
Acked-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: stable <stable@vger.kernel.org> # 4.2+
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/fhandle.c')
0 files changed, 0 insertions, 0 deletions