Arnd Bergmann 13aa38e291 xen kconfig: don't "select INPUT_XEN_KBDDEV_FRONTEND"
The Xen framebuffer driver selects the xen keyboard driver, so the latter
will be built-in if XEN_FBDEV_FRONTEND=y. However, when CONFIG_INPUT
is a loadable module, this configuration cannot work. On mainline kernels,
the symbol will be enabled but not used, while in combination with
a patch I have to detect such useless configurations, we get the
expected link failure:

drivers/input/built-in.o: In function `xenkbd_remove':
xen-kbdfront.c:(.text+0x2f0): undefined reference to `input_unregister_device'
xen-kbdfront.c:(.text+0x30e): undefined reference to `input_unregister_device'

This removes the extra "select", as it just causes more trouble than
it helps. In theory, some defconfig file might break if it has
XEN_FBDEV_FRONTEND in it but not INPUT_XEN_KBDDEV_FRONTEND. The Kconfig
fragment we ship in the kernel (kernel/configs/xen.config) however
already enables both, and anyone using an old .config file would
keep having both enabled.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Suggested-by: David Vrabel <david.vrabel@citrix.com>
Fixes: 36c1132e34bd ("xen kconfig: fix select INPUT_XEN_KBDDEV_FRONTEND")
Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
2016-03-11 13:37:02 +02:00
..
2015-10-08 12:24:12 +03:00
2016-01-22 18:04:28 -05:00
2016-02-29 18:56:03 +02:00
2014-07-01 13:32:30 +03:00
2016-02-26 13:28:35 +02:00
2015-06-23 16:23:30 -07:00
2016-02-26 13:28:35 +02:00
2016-02-26 13:28:35 +02:00
2016-02-26 13:28:35 +02:00
2015-10-08 12:19:39 +03:00
2014-12-14 16:10:09 -08:00
2016-02-26 12:16:58 +02:00
2015-02-11 17:06:05 -08:00
2016-02-26 13:28:35 +02:00
2015-03-02 13:17:24 +02:00
2015-11-10 10:00:09 -08:00
2015-08-20 12:03:53 +03:00