From: Len Brown <lenb@kernel.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
akpm@linux-foundation.org, linux-acpi@vger.kernel.org,
hpa@zytor.com, mingo@elte.hu, mjg59@srcf.ucam.org,
tglx@linutronix.de
Subject: Re: [patch 1/8] x86: oqo: depends on INPUT_POLLDEV
Date: Mon, 20 Apr 2009 00:27:40 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0904200026490.10996@localhost.localdomain> (raw)
In-Reply-To: <49E4C700.6010309@oracle.com>
> >>
> >> drivers/platform/x86/Kconfig | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff -puN drivers/platform/x86/Kconfig~x86-oqo-depends-on-input_polldev
> >> drivers/platform/x86/Kconfig ---
> >> a/drivers/platform/x86/Kconfig~x86-oqo-depends-on-input_polldev +++
> >> a/drivers/platform/x86/Kconfig
> >> @@ -137,7 +137,7 @@ config MSI_LAPTOP
> >> config OQO_WMI
> >> tristate "OQO WMI extras"
> >> depends on ACPI_WMI
> >> - depends on INPUT
> >> + depends on INPUT && INPUT_POLLDEV
> >
> > Make it "select INPUT_POLLDEV". Input-polldev is just a library code, users
> > should not have to select it for some drivers to become available.
>
>
> Did the OQO_WMI stuff go away? I can't seem to find it anywhere.
yeah, i droppped it from my test tree while distracted with the 2.6.30
merge. it is back now.
-Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-04-20 4:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 19:55 [patch 1/8] x86: oqo: depends on INPUT_POLLDEV akpm
2009-03-16 3:05 ` Len Brown
2009-04-14 2:16 ` Dmitry Torokhov
2009-04-14 17:25 ` Randy Dunlap
2009-04-20 4:27 ` Len Brown [this message]
2009-05-20 1:22 ` x86 platform: oqo: select INPUT_POLLDEV Randy Dunlap
2009-05-20 2:28 ` Dmitry Torokhov
2009-05-27 20:34 ` Len Brown
2009-05-27 23:03 ` Matthew Garrett
2009-05-30 0:52 ` Len Brown
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=alpine.LFD.2.00.0904200026490.10996@localhost.localdomain \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=randy.dunlap@oracle.com \
--cc=tglx@linutronix.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