From: Miloslav Trmac <mitr@volny.cz>
To: "Yu, Luming" <luming.yu@intel.com>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
Linus Torvalds <torvalds@osdl.org>,
Vojtech Pavlik <vojtech@suse.cz>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Brown, Len" <len.brown@intel.com>
Subject: Re: [git pull 02/14] Add Wistron driver
Date: Tue, 06 Dec 2005 09:15:49 +0100 [thread overview]
Message-ID: <439548B5.9030603@volny.cz> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F840A53FC2D@pdsmsx403>
Yu, Luming wrote:
>>If your laptop provides the hotkey events via ACPI, simply don't use
>>wistron_btns.
>
>
> wistron driver should be disabled if acpi hotkey enabled.
It is implicitly disabled because it contains DMI ids of known laptops,
and its module_init() fails with -ENODEV when used on other hardware,
before ever touching the BIOS.
I therefore can't see how it could break anything unless you have
explicitly supplied module parameters to override this check.
Mirek
next prev parent reply other threads:[~2005-12-06 8:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 7:35 [git pull 02/14] Add Wistron driver Yu, Luming
2005-12-06 8:15 ` Miloslav Trmac [this message]
2005-12-06 8:30 ` Miloslav Trmac
-- strict thread matches above, loose matches on Subject: below --
2005-12-06 8:57 Yu, Luming
2005-12-07 14:43 ` Miloslav Trmac
2005-12-06 8:38 Yu, Luming
2005-12-06 8:11 Yu, Luming
2005-12-06 15:21 ` Dmitry Torokhov
2005-12-11 13:10 ` Bernhard Rosenkraenzer
2005-12-11 22:40 ` Vojtech Pavlik
2005-12-12 8:13 ` Andrew Morton
2005-12-12 9:14 ` Stefan Seyfried
2005-12-12 9:38 ` Andrew Morton
2005-12-12 11:22 ` Stefan Seyfried
2005-12-12 11:33 ` Andrew Morton
2005-11-20 6:36 [git pull 00/14] Input updates for 2.6.15 Dmitry Torokhov
2005-11-20 6:36 ` [git pull 02/14] Add Wistron driver Dmitry Torokhov
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=439548B5.9030603@volny.cz \
--to=mitr@volny.cz \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=torvalds@osdl.org \
--cc=vojtech@suse.cz \
/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