diff options
| author |   Wolfram Sang <w.sang@pengutronix.de> | 2011-07-14 12:53:00 +0200 |
|---|---|---|
| committer |   Wim Van Sebroeck <wim@iguana.be> | 2011-07-26 21:21:16 +0000 |
| commit | 2fc5d52b212b58a5b48af19d85cb60971aa1aa4b (patch) | |
| tree | b19d4cb19adb0f384a005942050ab0ef8986a1af /drivers/watchdog/iTCO_wdt.c | |
| parent | watchdog: sp805: Flush posted writes in enable/disable. (diff) | |
| download | linux-dev-2fc5d52b212b58a5b48af19d85cb60971aa1aa4b.tar.xz linux-dev-2fc5d52b212b58a5b48af19d85cb60971aa1aa4b.zip | |
watchdog: remove empty pm-functions
While checking what watchdog drivers usually do in suspend/resume to
spot common behaviour for the watchdog framework, I found these drivers
which do nothing but add some cruft. Remove it, it is superfluous. New
approaches should probably be done with pm_ops anyway.
Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Signed-off-by: Wim Van Sebroeck <wim@iguana.be>
Diffstat (limited to 'drivers/watchdog/iTCO_wdt.c')
| -rw-r--r-- | drivers/watchdog/iTCO_wdt.c | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/drivers/watchdog/iTCO_wdt.c b/drivers/watchdog/iTCO_wdt.c index 1190bf158f8e..751a591684da 100644 --- a/drivers/watchdog/iTCO_wdt.c +++ b/drivers/watchdog/iTCO_wdt.c @@ -923,15 +923,10 @@ static void iTCO_wdt_shutdown(struct platform_device *dev) iTCO_wdt_stop(); } -#define iTCO_wdt_suspend NULL -#define iTCO_wdt_resume NULL - static struct platform_driver iTCO_wdt_driver = { .probe = iTCO_wdt_probe, .remove = __devexit_p(iTCO_wdt_remove), .shutdown = iTCO_wdt_shutdown, - .suspend = iTCO_wdt_suspend, - .resume = iTCO_wdt_resume, .driver = { .owner = THIS_MODULE, .name = DRV_NAME, |