From: "Yu, Luming" <luming.yu@intel.com>
To: "Matthew Garrett" <mjg59@srcf.ucam.org>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Stelian Pop" <stelian@popies.net>, <thoenig@suse.de>,
<borislav@users.sourceforge.net>, <john@neggie.net>,
<tauber@informatik.hu-berlin.de>, <sziwan@hell.org.pl>,
"Brown, Len" <len.brown@intel.com>
Subject: RE: acpi hotkey sysfs support
Date: Wed, 19 Apr 2006 09:48:37 +0800 [thread overview]
Message-ID: <554C5F4C5BA7384EB2B412FD46A3BAD1331CCB@pdsmsx411.ccr.corp.intel.com> (raw)
Hi Garrett,
Since you have provided generic backlight support for ASUS/IBM/Toshiba
acpi driver, which can reduce the unnecessary interface complexity in
platform specific acpi driver for brightness control, do you plan to do
same
thing for Ouptput switch, sound volume control..? Moreover, do you
think the proposal below still make sense?
--Luming
>Subject: acpi hotkey sysfs support
>
>Hello all,
>
>I have created a place under sysfs to have a unified place
>to gather user input for common hotkey features.
>http://bugzilla.kernel.org/show_bug.cgi?id=5749#c10
>
>All of you are owner of a specific acpi hotkey driver.
>Would you like to use that sysfs support to reduce the
>unnecessary interface complexity.
>
>Thanks a lot
>Luming
>-
next reply other threads:[~2006-04-19 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 1:48 Yu, Luming [this message]
[not found] <20060419130719.GA2599@ucw.cz>
2006-04-21 19:16 ` Pavel Machek
2006-04-21 19:20 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-04-17 3:09 Yu, Luming
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=554C5F4C5BA7384EB2B412FD46A3BAD1331CCB@pdsmsx411.ccr.corp.intel.com \
--to=luming.yu@intel.com \
--cc=borislav@users.sourceforge.net \
--cc=john@neggie.net \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=stelian@popies.net \
--cc=sziwan@hell.org.pl \
--cc=tauber@informatik.hu-berlin.de \
--cc=thoenig@suse.de \
/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
all inboxes | Powered by JetHome®