From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: wim@linux-watchdog.org, linux@roeck-us.net,
linux-watchdog@vger.kernel.org
Subject: [PATCH 3/3] watchdog: iTCO_wdt: use pm_ptr()
Date: Tue, 17 Nov 2020 16:22:14 +0100 [thread overview]
Message-ID: <20201117152214.32244-3-info@metux.net> (raw)
In-Reply-To: <20201117152214.32244-1-info@metux.net>
Reduce a little bit of boilerplate by using pm_ptr().
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
---
drivers/watchdog/iTCO_wdt.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/watchdog/iTCO_wdt.c b/drivers/watchdog/iTCO_wdt.c
index edc588a06ae6..660fc262fbc0 100644
--- a/drivers/watchdog/iTCO_wdt.c
+++ b/drivers/watchdog/iTCO_wdt.c
@@ -636,16 +636,13 @@ static const struct dev_pm_ops iTCO_wdt_pm = {
.resume_noirq = iTCO_wdt_resume_noirq,
};
-#define ITCO_WDT_PM_OPS (&iTCO_wdt_pm)
-#else
-#define ITCO_WDT_PM_OPS NULL
#endif /* CONFIG_PM_SLEEP */
static struct platform_driver iTCO_wdt_driver = {
.probe = iTCO_wdt_probe,
.driver = {
.name = DRV_NAME,
- .pm = ITCO_WDT_PM_OPS,
+ .pm = pm_ptr(&iTCO_wdt_pm),
},
};
--
2.11.0
next prev parent reply other threads:[~2020-11-17 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 15:22 [PATCH 1/3] watchdog: iTCO_wdt: use module_platform_device() macro Enrico Weigelt, metux IT consult
2020-11-17 15:22 ` [PATCH 2/3] watchdog: iTCO_wdt: use dev_*() instead of pr_*() for logging Enrico Weigelt, metux IT consult
2021-06-09 20:32 ` Bjorn Helgaas
2021-06-09 23:54 ` Guenter Roeck
2021-06-14 17:55 ` Enrico Weigelt, metux IT consult
2021-06-15 14:51 ` Bjorn Helgaas
2020-11-17 15:22 ` Enrico Weigelt, metux IT consult [this message]
2020-11-30 22:17 ` [PATCH 3/3] watchdog: iTCO_wdt: use pm_ptr() Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201117152214.32244-3-info@metux.net \
--to=info@metux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@linux-watchdog.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).