From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Jeremy Katz <katzj@redhat.com>,
linux-kernel@vger.kernel.org, davej@redhat.com,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH] Map volume and brightness events on thinkpads
Date: Tue, 16 Oct 2007 20:20:10 +0100 [thread overview]
Message-ID: <20071016192010.GA26692@srcf.ucam.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0710161208340.6887@woody.linux-foundation.org>
On Tue, Oct 16, 2007 at 12:14:32PM -0700, Linus Torvalds wrote:
> IOW, I think the thinkpad issue (and others like it) should be fixed by
> splitting up the KEY_VOLUMEUP "key" into separate KEY_VOLUMEUP and
> KEY_VOLUMEUP_NOTIFY key events, so that downstream user mode (and the
> kernel itself, for that matter) can know whether it's a informational
> message or whether it should be acted upon.
In principle I agree, but userspace already handles it. While it's
certainly more correct, I'm not sure it provides any other real
advantage.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2007-10-16 19:20 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 20:45 [PATCH] Map volume and brightness events on thinkpads Jeremy Katz
2007-10-15 21:07 ` Henrique de Moraes Holschuh
2007-10-15 21:27 ` Jeremy Katz
2007-10-16 9:12 ` Henrique de Moraes Holschuh
2007-10-15 21:43 ` Arjan van de Ven
2007-10-16 3:38 ` Jesse Barnes
2007-10-16 8:36 ` Henrique de Moraes Holschuh
2007-10-16 8:49 ` Jesse Barnes
2007-10-16 9:18 ` Henrique de Moraes Holschuh
2007-10-17 2:40 ` Jesse Barnes
2007-10-17 6:25 ` Henrique de Moraes Holschuh
2007-10-17 6:32 ` Jesse Barnes
2007-10-17 6:39 ` Henrique de Moraes Holschuh
2007-10-16 13:00 ` Matthew Garrett
2007-10-16 14:11 ` Henrique de Moraes Holschuh
2007-10-16 14:21 ` Matthew Garrett
2007-10-16 14:31 ` Henrique de Moraes Holschuh
2007-10-16 14:40 ` Matthew Garrett
2007-10-16 16:56 ` Henrique de Moraes Holschuh
2007-10-16 18:46 ` Matthew Garrett
2007-10-16 19:14 ` Linus Torvalds
2007-10-16 19:20 ` Matthew Garrett [this message]
2007-10-16 20:02 ` Henrique de Moraes Holschuh
2007-10-16 20:15 ` Dmitry Torokhov
2007-10-16 20:12 ` Dmitry Torokhov
2007-10-16 20:11 ` Jeremy Katz
2007-10-16 20:19 ` Dmitry Torokhov
2007-10-16 20:32 ` Linus Torvalds
2007-10-17 15:57 ` Dmitry Torokhov
2007-10-17 16:28 ` Matthew Garrett
2007-10-17 17:35 ` Henrique de Moraes Holschuh
2007-10-17 18:59 ` Dmitry Torokhov
2007-10-17 20:42 ` Henrique de Moraes Holschuh
2007-10-18 14:37 ` Dmitry Torokhov
2007-10-18 22:39 ` Henrique de Moraes Holschuh
2007-10-23 15:54 ` Dmitry Torokhov
2007-10-23 23:34 ` Henrique de Moraes Holschuh
2007-10-16 20:48 ` Kok, Auke
2007-10-16 20:55 ` Matthew Garrett
2007-10-16 21:18 ` Dmitry Torokhov
2007-10-16 20:32 ` Dave Airlie
2007-10-16 14:27 ` Dmitry Torokhov
2007-10-16 14:54 ` Matthew Garrett
2007-10-16 15:54 ` Dmitry Torokhov
2007-10-16 15:59 ` Matthew Garrett
2007-10-16 18:53 ` Matthew Garrett
2007-10-16 19:23 ` Renato S. Yamane
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=20071016192010.GA26692@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=davej@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=katzj@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.