From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
gregkh@suse•de, driverdevel <devel@driverdev•osuosl.org>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
naveen.gaddipati@stericsson•com, js.ha@stericsson•com
Subject: [PATCH -next] staging: fix ste_rmi4 build, depends on INPUT
Date: Fri, 12 Nov 2010 14:47:02 -0800 [thread overview]
Message-ID: <20101112144702.117505ee.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20101111125655.15fa7188.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle•com>
The synaptics_i2c_rmi4 driver uses input_*() interfaces,
so it should depend on INPUT to fix its build errors:
ERROR: "input_event" [drivers/staging/ste_rmi4/synaptics_i2c_rmi4.ko] undefined!
ERROR: "input_free_device" [drivers/staging/ste_rmi4/synaptics_i2c_rmi4.ko] undefined!
ERROR: "input_register_device" [drivers/staging/ste_rmi4/synaptics_i2c_rmi4.ko] undefined!
ERROR: "input_set_abs_params" [drivers/staging/ste_rmi4/synaptics_i2c_rmi4.ko] undefined!
ERROR: "input_allocate_device" [drivers/staging/ste_rmi4/synaptics_i2c_rmi4.ko] undefined!
ERROR: "input_unregister_device" [drivers/staging/ste_rmi4/synaptics_i2c_rmi4.ko] undefined!
Signed-off-by: Randy Dunlap <randy.dunlap@oracle•com>
Cc: naveen.gaddipati@stericsson•com, js.ha@stericsson•com
---
drivers/staging/ste_rmi4/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20101111.orig/drivers/staging/ste_rmi4/Kconfig
+++ linux-next-20101111/drivers/staging/ste_rmi4/Kconfig
@@ -1,6 +1,6 @@
config TOUCHSCREEN_SYNAPTICS_I2C_RMI4
tristate "Synaptics i2c rmi4 touchscreen"
- depends on I2C
+ depends on I2C && INPUT
help
Say Y here if you have a Synaptics RMI4 and
want to enable support for the built-in touchscreen.
prev parent reply other threads:[~2010-11-12 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 1:56 linux-next: Tree for November 11 Stephen Rothwell
2010-11-11 17:48 ` linux-next: Tree for November 11 (unifdef) Randy Dunlap
2010-11-11 18:26 ` Tony Finch
2010-11-11 18:44 ` [PATCH -next] staging/easycap: make module params private/static, fix build Randy Dunlap
2010-11-11 22:02 ` R.M. Thomas
2010-11-11 22:18 ` Randy Dunlap
2010-11-12 10:30 ` R.M. Thomas
2010-11-12 22:47 ` 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=20101112144702.117505ee.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=devel@driverdev$(echo .)osuosl.org \
--cc=gregkh@suse$(echo .)de \
--cc=js.ha@stericsson$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=naveen.gaddipati@stericsson$(echo .)com \
--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