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 INPUT_SPARSEKMAP
Date: Tue, 13 Apr 2010 09:45:44 -0700 [thread overview]
Message-ID: <20100413094544.38369da9.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100413163427.8acd04e5.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle•com>
When EEEPC_WMI=y and INPUT_SPARSEKMAP=m, the build fails,
so make EEEPC_WMI depend on INPUT_SPARSEKMAP.
eeepc-wmi.c:(.text+0x28d1a9): undefined reference to `sparse_keymap_setup'
eeepc-wmi.c:(.text+0x28d1f9): undefined reference to `sparse_keymap_free'
eeepc-wmi.c:(.text+0x28d2e0): undefined reference to `sparse_keymap_report_event'
eeepc-wmi.c:(.init.text+0x17069): undefined reference to `sparse_keymap_free'
eeepc-wmi.c:(.exit.text+0x2bae): undefined reference to `sparse_keymap_free'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle•com>
---
drivers/platform/x86/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20100413.orig/drivers/platform/x86/Kconfig
+++ linux-next-20100413/drivers/platform/x86/Kconfig
@@ -388,7 +388,7 @@ config EEEPC_LAPTOP
config EEEPC_WMI
tristate "Eee PC WMI Hotkey Driver (EXPERIMENTAL)"
depends on ACPI_WMI
- depends on INPUT
+ depends on INPUT && INPUT_SPARSEKMAP
depends on EXPERIMENTAL
---help---
Say Y here if you want to support WMI-based hotkeys on Eee PC laptops.
next prev parent reply other threads:[~2010-04-13 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 6:34 linux-next: Tree for April 13 Stephen Rothwell
2010-04-13 16:45 ` Randy Dunlap [this message]
2010-04-13 22:39 ` [PATCH -next] eeepc-wmi: depends on INPUT_SPARSEKMAP Dmitry Torokhov
2010-04-14 12:34 ` 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=20100413094544.38369da9.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mjg@redhat$(echo .)com \
--cc=platform-driver-x86@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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