From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Matthew Garrett <mjg@redhat.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org
Subject: [PATCH -next] eeepc-wmi: depends on BACKLIGHT_CLASS_DEVICE
Date: Fri, 7 May 2010 11:24:11 -0700 [thread overview]
Message-ID: <20100507112411.0212242d.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100507155520.75026a8b.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
eeepc-wmi uses backlight*() interfaces so it should depend on
BACKLIGHT_CLASS_DEVICE.
eeepc-wmi.c:(.text+0x2d7f54): undefined reference to `backlight_force_update'
eeepc-wmi.c:(.text+0x2d8012): undefined reference to `backlight_device_register'
eeepc-wmi.c:(.devinit.text+0x1c31c): undefined reference to `backlight_device_unregister'
eeepc-wmi.c:(.devexit.text+0x2f8b): undefined reference to `backlight_device_unregister'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
drivers/platform/x86/Kconfig | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20100507.orig/drivers/platform/x86/Kconfig
+++ linux-next-20100507/drivers/platform/x86/Kconfig
@@ -390,6 +390,7 @@ config EEEPC_WMI
depends on ACPI_WMI
depends on INPUT
depends on EXPERIMENTAL
+ depends on BACKLIGHT_CLASS_DEVICE
select INPUT_SPARSEKMAP
---help---
Say Y here if you want to support WMI-based hotkeys on Eee PC laptops.
next prev parent reply other threads:[~2010-05-07 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 5:55 linux-next: Tree for May 7 Stephen Rothwell
2010-05-07 15:55 ` linux-next: Tree for May 7 (apei) Randy Dunlap
2010-05-10 0:33 ` Huang Ying
2010-05-07 18:22 ` [PATCH -next] media: vivi and mem2mem_testdev need slab.h to build Randy Dunlap
2010-05-07 18:24 ` Randy Dunlap [this message]
2010-05-07 18:26 ` [PATCH -next] eeepc-wmi: depends on BACKLIGHT_CLASS_DEVICE Matthew Garrett
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=20100507112411.0212242d.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).