From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, Hong Liu <hong.liu@intel•com>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Matthew Garrett <mjg@redhat•com>,
platform-driver-x86@vger•kernel.org
Subject: [PATCH -next] platform/x86: intel_mid_powerbutton needs INPUT
Date: Wed, 16 Feb 2011 14:31:02 -0800 [thread overview]
Message-ID: <20110216143102.04bc6754.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110216165321.c8238ed5.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle•com>
intel_mid_powerbtn.c uses input interfaces, so it should depend
on INPUT to fix build errors when CONFIG_INPUT is not enabled:
intel_mid_powerbtn.c:(.text+0x56ca8f): undefined reference to `input_event'
intel_mid_powerbtn.c:(.devinit.text+0x2e7b4): undefined reference to `input_allocate_device'
intel_mid_powerbtn.c:(.devinit.text+0x2e7ff): undefined reference to `input_set_capability'
intel_mid_powerbtn.c:(.devinit.text+0x2e84a): undefined reference to `input_register_device'
intel_mid_powerbtn.c:(.devinit.text+0x2e88b): undefined reference to `input_free_device'
intel_mid_powerbtn.c:(.devexit.text+0x42f0): undefined reference to `input_unregister_device'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Hong Liu <hong.liu@intel•com>
---
drivers/platform/x86/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20110216.orig/drivers/platform/x86/Kconfig
+++ linux-next-20110216/drivers/platform/x86/Kconfig
@@ -607,7 +607,7 @@ config INTEL_MFLD_THERMAL
config INTEL_MID_POWER_BUTTON
tristate "power button driver for Intel MID platforms"
- depends on INTEL_SCU_IPC
+ depends on INTEL_SCU_IPC && INPUT
help
This driver handles the power button on the Intel MID platforms.
prev parent reply other threads:[~2011-02-16 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 5:53 linux-next: Tree for February 16 Stephen Rothwell
2011-02-16 22:31 ` Randy Dunlap [this message]
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=20110216143102.04bc6754.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=hong.liu@intel$(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