[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140526210211.GA23548@spo001.leaseweb.com>
Date: Mon, 26 May 2014 23:02:11 +0200
From: Wim Van Sebroeck <wim@...ana.be>
To: Arnd Bergmann <arnd@...db.de>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-watchdog@...r.kernel.org
Subject: Re: [PATCH] watchdog: iop_wdt only builds for mach-iop13xx
Hi Arnd,
> All three iop variants we support in Linux (iop32x, iop33x and
> iop13xx) seem to have support for the watchdog hardware, but this
> driver fails to build for the first two of these because it
> uses the IOP13XX_WDTCR_IB_RESET macro that is only defined for
> iop13xx.
>
> This clarifies the dependency in Kconfig to avoid randconfig
> build errors. It is unlikely that anyone will ever miss support
> for this driver on the ancient iop3xx platforms, so we don't
> need to bother trying to fix it properly.
>
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
> Cc: Wim Van Sebroeck <wim@...ana.be>
> Cc: linux-watchdog@...r.kernel.org
> ---
> drivers/watchdog/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index 2b4c1fc..e244548 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
> @@ -272,7 +272,7 @@ config PNX4008_WATCHDOG
>
> config IOP_WATCHDOG
> tristate "IOP Watchdog"
> - depends on PLAT_IOP
> + depends on ARCH_IOP13XX
> select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
> help
> Say Y here if to include support for the watchdog timer
Patch has been added to linux-watchdog-next.
Kind regards,
Wim.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists