On Wed, May 25, 2016 at 08:37:48AM +0200, Wolfram Sang wrote:
> From: Wolfram Sang
>
> If we leave set_timeout empty, the core will do exactly what is
> implemented here anyway.
>
> Signed-off-by: Wolfram Sang
Reviewed-by: Guenter Roeck
> ---
> drivers/watchdog/softdog.c | 7 ---
> 1 file changed, 7 deletions(-)
>
> diff --git a/drivers/watchdog/softdog.c b/drivers/watchdog/softdog.c
> index ab0e02fc81a276..5e3a30b99d4415 100644
> --- a/drivers/watchdog/softdog.c
> +++ b/drivers/watchdog/softdog.c
> @@ -87,12 +87,6 @@ static int softdog_stop(struct watchdog_device *w)
> return 0;
> }
>
> -static int softdog_set_timeout(struct watchdog_device *w, unsigned int t)
> -{
> - w->timeout = t;
> - return 0;
> -}
> -
> static struct watchdog_info softdog_info = {
> .identity = "Software Watchdog",
> .options = WDIOF_SETTIMEOUT | WDIOF_KEEPALIVEPING | WDIOF_MAGICCLOSE,
> @@ -102,7 +96,6 @@ static struct watchdog_ops softdog_ops = {
> .owner = THIS_MODULE,
> .start = softdog_ping,
> .stop = softdog_stop,
> - .set_timeout = softdog_set_timeout,
> };
>
> static struct watchdog_device softdog_dev = {
> --
> 2.8.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html