]> www.infradead.org Git - users/jedix/linux-maple.git/commit
xen kconfig: don't "select INPUT_XEN_KBDDEV_FRONTEND"
authorArnd Bergmann <arnd@arndb.de>
Tue, 16 Feb 2016 15:03:23 +0000 (16:03 +0100)
committerDhaval Giani <dhaval.giani@oracle.com>
Fri, 20 Jan 2017 22:22:01 +0000 (17:22 -0500)
commit96625a7f76a0e94641f6716e4f55863bdc91f0ac
tree716fbf3bb159281fc06d2698470abe82c29c1564
parent1e52892396c1d407ddccab6f7ebafaf14b26ae0b
xen kconfig: don't "select INPUT_XEN_KBDDEV_FRONTEND"

Orabug: 25308064

[ Upstream commit 13aa38e291bdd4e4018f40dd2f75e464814dcbf3 ]

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>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
(cherry picked from commit 372574134cc15a03608d87a3577885b049e40db3)
Signed-off-by: Dhaval Giani <dhaval.giani@oracle.com>
drivers/video/fbdev/Kconfig