From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Cc: Jiri Slaby <jslaby@suse.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vt: fix Scroll Lock LED trigger name
Date: Wed, 16 Nov 2016 08:24:42 +0100 [thread overview]
Message-ID: <20161116072442.GA19957@kroah.com> (raw)
In-Reply-To: <e8a3a0ac-1f41-be9a-a943-59a085d01c71@maciej.szmigiero.name>
On Wed, Nov 16, 2016 at 12:55:57AM +0100, Maciej S. Szmigiero wrote:
> 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>
> ---
> drivers/tty/vt/keyboard.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/vt/keyboard.c b/drivers/tty/vt/keyboard.c
> index d5d81d4d3c04..3dd6a491cdba 100644
> --- a/drivers/tty/vt/keyboard.c
> +++ b/drivers/tty/vt/keyboard.c
> @@ -982,7 +982,7 @@ static void kbd_led_trigger_activate(struct led_classdev *cdev)
> KBD_LED_TRIGGER((_led_bit) + 8, _name)
>
> static struct kbd_led_trigger kbd_led_triggers[] = {
> - KBD_LED_TRIGGER(VC_SCROLLOCK, "kbd-scrollock"),
> + KBD_LED_TRIGGER(VC_SCROLLOCK, "kbd-scrolllock"),
> KBD_LED_TRIGGER(VC_NUMLOCK, "kbd-numlock"),
> KBD_LED_TRIGGER(VC_CAPSLOCK, "kbd-capslock"),
> KBD_LED_TRIGGER(VC_KANALOCK, "kbd-kanalock"),
So, how far back should this change be backported to?
thanks,
greg k-h
next prev parent reply other threads:[~2016-11-16 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 23:55 [PATCH] vt: fix Scroll Lock LED trigger name Maciej S. Szmigiero
2016-11-16 0:19 ` Samuel Thibault
2016-11-16 7:24 ` Greg Kroah-Hartman [this message]
2016-11-16 8:10 ` Samuel Thibault
2016-11-16 8:15 ` Greg Kroah-Hartman
2016-12-05 13:47 ` Pavel Machek
2016-12-05 16:23 ` Samuel Thibault
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161116072442.GA19957@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
--cc=samuel.thibault@ens-lyon.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.