summaryrefslogtreecommitdiffstats
path: root/drivers/watchdog/Kconfig
diff options
context:
space:
mode:
authorRadu Rendec <radu.rendec@gmail.com>2018-02-19 14:38:51 +0000
committerWim Van Sebroeck <wim@linux-watchdog.org>2018-02-19 17:44:00 +0100
commit4cd6764495f2b6c2d3dc4fdd339f78764f7995d5 (patch)
tree5c305cc61791af75305d699f8322869b4a9adc65 /drivers/watchdog/Kconfig
parent7e2e5158e700f2196dff3b68ac07405575e09c22 (diff)
downloadlinux-4cd6764495f2b6c2d3dc4fdd339f78764f7995d5.tar.gz
linux-4cd6764495f2b6c2d3dc4fdd339f78764f7995d5.tar.bz2
linux-4cd6764495f2b6c2d3dc4fdd339f78764f7995d5.zip
watchdog: xen_wdt: fix potential build failure
xen_wdt uses watchdog core functions (from watchdog_core.c) and, when compiled without CONFIG_WATCHDOG_CORE being set, it produces the following build error: ERROR: "devm_watchdog_register_device" [drivers/watchdog/xen_wdt.ko] undefined! ERROR: "watchdog_init_timeout" [drivers/watchdog/xen_wdt.ko] undefined! Fix this by selecting CONFIG_WATCHDOG_CORE when CONFIG_XEN_WDT is set. Fixes: 18cffd68e0c4 ("watchdog: xen_wdt: use the watchdog subsystem") Signed-off-by: Radu Rendec <radu.rendec@gmail.com> Reviewed-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Wim Van Sebroeck <wim@iguana.be>
Diffstat (limited to 'drivers/watchdog/Kconfig')
-rw-r--r--drivers/watchdog/Kconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
index 56f9e203049e..3d984cdea0ca 100644
--- a/drivers/watchdog/Kconfig
+++ b/drivers/watchdog/Kconfig
@@ -1839,6 +1839,7 @@ config WATCHDOG_SUN4V
config XEN_WDT
tristate "Xen Watchdog support"
depends on XEN
+ select WATCHDOG_CORE
help
Say Y here to support the hypervisor watchdog capability provided
by Xen 4.0 and newer. The watchdog timeout period is normally one