From: "H. Peter Anvin" <hpa@zytor.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk, mgarski@post.pl
Subject: Re: [PATCH] kbd: (#7063) make CapsLock work as expected even for non-ASCII
Date: Fri, 20 Nov 2009 13:27:48 -0800 [thread overview]
Message-ID: <4B0709D4.6010305@zytor.com> (raw)
In-Reply-To: <20091120204612.GA31728@elf.ucw.cz>
On 11/20/2009 12:46 PM, Pavel Machek wrote:
>
> Like this... But it should probably be slightly more complex -- like
> making numlock/capslock/scrollock leds into trigers, and then
> move input LED lowlevels into drivers/led...
>
In particular, all keyboard modifiers should be available triggers.
-hpa
next prev parent reply other threads:[~2009-11-20 21:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 13:51 [PATCH] kbd: (#7063) make CapsLock work as expected even for non-ASCII Alexey Dobriyan
2009-11-16 14:40 ` Alan Cox
2009-11-16 19:08 ` Samuel Thibault
2009-11-16 19:07 ` Samuel Thibault
2009-11-16 19:53 ` Alexey Dobriyan
2009-11-16 22:27 ` Samuel Thibault
2009-11-16 22:53 ` Alexey Dobriyan
2009-11-16 23:04 ` Samuel Thibault
2009-11-16 22:54 ` Samuel Thibault
2009-11-16 23:05 ` Alexey Dobriyan
2009-11-16 23:15 ` Samuel Thibault
2009-11-17 11:55 ` Alexey Dobriyan
2009-11-17 13:23 ` Samuel Thibault
2009-11-19 13:18 ` Alexey Dobriyan
2009-11-19 13:28 ` Samuel Thibault
2009-11-19 13:37 ` Samuel Thibault
2009-11-19 15:07 ` H. Peter Anvin
2009-11-20 19:07 ` Pavel Machek
2009-11-20 20:46 ` Pavel Machek
2009-11-20 21:27 ` H. Peter Anvin [this message]
2010-02-21 5:01 ` [RFC,PATCH] Route kbd leds through the generic leds layer (Was: [PATCH] kbd: (#7063) make CapsLock work as expected even for non-ASCII) Samuel Thibault
2010-02-23 16:30 ` Pavel Machek
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=4B0709D4.6010305@zytor.com \
--to=hpa@zytor.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarski@post.pl \
--cc=pavel@ucw.cz \
--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.