From: CaT <cat@zip.com.au>
To: Philip Graham Willoughby <pgw99@doc.ic.ac.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH : LEDs - possibly the most pointless kernel subsystem ever
Date: Wed, 30 Jul 2003 16:36:57 +1000 [thread overview]
Message-ID: <20030730063657.GH1395@zip.com.au> (raw)
In-Reply-To: <20030729151701.GA6795@bodmin.doc.ic.ac.uk>
On Tue, Jul 29, 2003 at 04:17:03PM +0100, Philip Graham Willoughby wrote:
> Hi all,
>
> This patch adds an abstraction layer for programmable LED devices,
Would this (now or in the future) by any chance let one use the keyboard
leds for stuff without activating their num lock, caps lock and scroll
lock functionality? I'd like to use one of them (at least) as a network
traffic indicator but so far I get the sideffects of the functionality
being on also. Most annoying when typing. :/
--
"How can I not love the Americans? They helped me with a flat tire the
other day," he said.
- http://tinyurl.com/h6fo
next prev parent reply other threads:[~2003-07-30 6:37 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 15:17 PATCH : LEDs - possibly the most pointless kernel subsystem ever Philip Graham Willoughby
2003-07-29 18:00 ` Pavel Machek
2003-07-30 11:45 ` Jamey Hicks
2003-07-30 12:06 ` PATCH : LEDs - possibly the most pointless kernel subsystemever Ghozlane Toumi
2003-07-30 12:27 ` Philip Graham Willoughby
2003-07-30 12:39 ` Wichert Akkerman
2003-07-30 12:27 ` PATCH : LEDs - possibly the most pointless kernel subsystem ever Pavel Machek
2003-07-30 6:36 ` CaT [this message]
2003-07-30 13:00 ` Andries Brouwer
2003-07-30 13:20 ` CaT
2003-07-30 23:28 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-07-29 19:15 John Bradford
2003-07-29 19:51 ` Tim Hockin
2003-07-29 20:09 ` Joel Jaeggli
2003-07-29 21:20 ` Kent Borg
2003-07-29 21:44 ` Philip Graham Willoughby
2003-07-30 21:44 ` Mike Jagdis
2003-07-30 12:15 ` Pavel Machek
2003-07-29 20:38 John Bradford
2003-07-29 20:37 ` Andries Brouwer
2003-07-29 21:34 ` Philip Graham Willoughby
2003-07-29 20:40 ` Randolph Bentson
2003-07-29 21:15 ` Ryan Flowers
2003-07-29 20:43 ` Eli Carter
2003-07-30 6:09 ` Tomas Szepe
2003-07-30 6:37 ` Helge Deller
2003-07-30 12:27 "Andrey Borzenkov"
2003-07-30 15:50 John Bradford
2003-07-30 16:08 John Bradford
2003-07-30 17:44 ` Pavel Machek
2003-07-30 18:50 ` Marc Giger
2003-07-30 19:05 ` Herbert Pötzl
2003-07-30 22:22 ` Brian McGroarty
2003-07-30 18:56 ` Herbert Pötzl
2003-07-30 19:02 ` Pavel Machek
2003-07-30 19:06 ` Marc Giger
2003-07-30 19:16 ` Herbert Pötzl
2003-07-31 8:31 ` jw schultz
2003-07-30 18:50 John Bradford
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=20030730063657.GH1395@zip.com.au \
--to=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pgw99@doc.ic.ac.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox