From: Chen Gang <gang.chen.5i5j@gmail.com>
To: dmitry.torokhov@gmail.com
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
kys@microsoft.com, Martin Schwidefsky <schwidefsky@de.ibm.com>,
teg@jklm.no, Mischa.Jonker@synopsys.com, msalter@redhat.com,
linux-input@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Liqin Chen <liqin.linux@gmail.com>,
Richard Weinberger <richard@nod.at>,
Lennox Wu <lennox.wu@gmail.com>
Subject: [PATCH] drivers/input/serio/Kconfig: Let SERIO_ARC_PS2 and SERIO_OLPC_APSP depend on HAS_IOMEM
Date: Sun, 13 Jul 2014 20:00:33 +0800 [thread overview]
Message-ID: <53C274E1.3080804@gmail.com> (raw)
SERIO_ARC_PS2 and SERIO_OLPC_APSP need HAS_IOMEM, so let them depend on
HAS_IOMEM. The related error (with allmodconfig under score):
MODPOST 1365 modules
ERROR: "devm_ioremap_resource" [drivers/input/serio/olpc_apsp.ko] undefined!
ERROR: "devm_ioremap_resource" [drivers/input/serio/arc_ps2.ko] undefined!
Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
---
drivers/input/serio/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/input/serio/Kconfig b/drivers/input/serio/Kconfig
index bc2d474..449d45f 100644
--- a/drivers/input/serio/Kconfig
+++ b/drivers/input/serio/Kconfig
@@ -244,6 +244,7 @@ config SERIO_PS2MULT
config SERIO_ARC_PS2
tristate "ARC PS/2 support"
+ depends on HAS_IOMEM
help
Say Y here if you have an ARC FPGA platform with a PS/2
controller in it.
@@ -263,7 +264,7 @@ config SERIO_APBPS2
config SERIO_OLPC_APSP
tristate "OLPC AP-SP input support"
- depends on OLPC || COMPILE_TEST
+ depends on (OLPC || COMPILE_TEST) && HAS_IOMEM
help
Say Y here if you want support for the keyboard and touchpad included
in the OLPC XO-1.75 and XO-4 laptops.
--
1.7.11.7
reply other threads:[~2014-07-13 12:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53C274E1.3080804@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=Mischa.Jonker@synopsys.com \
--cc=benh@kernel.crashing.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kys@microsoft.com \
--cc=lennox.wu@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqin.linux@gmail.com \
--cc=msalter@redhat.com \
--cc=richard@nod.at \
--cc=schwidefsky@de.ibm.com \
--cc=teg@jklm.no \
/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).