Hi Rasmus, > bcm2835_wdt_set_timeout does exactly what the watchdog framework does > in the absence of a ->set_timeout callback (see watchdog_set_timeout > in watchdog_dev.c), so remove it. > > Signed-off-by: Rasmus Villemoes <rasmus.villemoes@xxxxxxxxx> > --- > drivers/watchdog/bcm2835_wdt.c | 7 ------- > 1 file changed, 7 deletions(-) > > diff --git a/drivers/watchdog/bcm2835_wdt.c b/drivers/watchdog/bcm2835_wdt.c > index 733e402..4dddd82 100644 > --- a/drivers/watchdog/bcm2835_wdt.c > +++ b/drivers/watchdog/bcm2835_wdt.c > @@ -82,12 +82,6 @@ static int bcm2835_wdt_stop(struct watchdog_device *wdog) > return 0; > } > > -static int bcm2835_wdt_set_timeout(struct watchdog_device *wdog, unsigned int t) > -{ > - wdog->timeout = t; > - return 0; > -} > - > static unsigned int bcm2835_wdt_get_timeleft(struct watchdog_device *wdog) > { > struct bcm2835_wdt *wdt = watchdog_get_drvdata(wdog); > @@ -100,7 +94,6 @@ static const struct watchdog_ops bcm2835_wdt_ops = { > .owner = THIS_MODULE, > .start = bcm2835_wdt_start, > .stop = bcm2835_wdt_stop, > - .set_timeout = bcm2835_wdt_set_timeout, > .get_timeleft = bcm2835_wdt_get_timeleft, > }; > > -- > 2.5.0 > This patch has been added to linux-watchdog-next. Kind regards, Wim. -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html