From: Guenter Roeck <linux@roeck-us.net>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] watchdog: kempld: Remove #ifdef guards for PM related functions
Date: Thu, 20 Oct 2022 15:00:29 -0700 [thread overview]
Message-ID: <20221020220029.GD4035307@roeck-us.net> (raw)
In-Reply-To: <20221020185047.1001522-5-paul@crapouillou.net>
On Thu, Oct 20, 2022 at 07:50:47PM +0100, Paul Cercueil wrote:
> Use the pm_ptr() macro to handle the .suspend/.resume callbacks.
>
> This macro allows the suspend and resume functions to be automatically
> dropped by the compiler when CONFIG_SUSPEND is disabled, without having
> to use #ifdef guards. Not using #ifdef guards means that the code is
> always compiled independently of any Kconfig option, and thanks to that
> bugs and regressions are easier to catch.
>
> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> drivers/watchdog/kempld_wdt.c | 11 ++---------
> 1 file changed, 2 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/watchdog/kempld_wdt.c b/drivers/watchdog/kempld_wdt.c
> index 40bd518ed873..e6c7a2906680 100644
> --- a/drivers/watchdog/kempld_wdt.c
> +++ b/drivers/watchdog/kempld_wdt.c
> @@ -75,9 +75,7 @@ struct kempld_wdt_data {
> struct watchdog_device wdd;
> unsigned int pretimeout;
> struct kempld_wdt_stage stage[KEMPLD_WDT_MAX_STAGES];
> -#ifdef CONFIG_PM
> u8 pm_status_store;
> -#endif
> };
>
> #define DEFAULT_TIMEOUT 30 /* seconds */
> @@ -495,7 +493,6 @@ static int kempld_wdt_probe(struct platform_device *pdev)
> return 0;
> }
>
> -#ifdef CONFIG_PM
> /* Disable watchdog if it is active during suspend */
> static int kempld_wdt_suspend(struct platform_device *pdev,
> pm_message_t message)
> @@ -531,18 +528,14 @@ static int kempld_wdt_resume(struct platform_device *pdev)
> else
> return kempld_wdt_stop(wdd);
> }
> -#else
> -#define kempld_wdt_suspend NULL
> -#define kempld_wdt_resume NULL
> -#endif
>
> static struct platform_driver kempld_wdt_driver = {
> .driver = {
> .name = "kempld-wdt",
> },
> .probe = kempld_wdt_probe,
> - .suspend = kempld_wdt_suspend,
> - .resume = kempld_wdt_resume,
> + .suspend = pm_ptr(kempld_wdt_suspend),
> + .resume = pm_ptr(kempld_wdt_resume),
> };
>
> module_platform_driver(kempld_wdt_driver);
> --
> 2.35.1
>
prev parent reply other threads:[~2022-10-20 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 18:50 [PATCH 0/4] watchdog: Remove #ifdef guards for PM functions Paul Cercueil
2022-10-20 18:50 ` [PATCH 1/4] watchdog: at91rm9200: Remove #ifdef guards for PM related functions Paul Cercueil
2022-10-20 21:59 ` Guenter Roeck
2022-10-21 7:21 ` Claudiu.Beznea
2022-10-20 18:50 ` [PATCH 2/4] watchdog: twl4030: " Paul Cercueil
2022-10-20 21:59 ` Guenter Roeck
2022-10-20 18:50 ` [PATCH 3/4] watchdog: omap: " Paul Cercueil
2022-10-20 19:22 ` Aaro Koskinen
2022-10-20 22:00 ` Guenter Roeck
2022-10-20 18:50 ` [PATCH 4/4] watchdog: kempld: " Paul Cercueil
2022-10-20 22:00 ` Guenter Roeck [this message]
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=20221020220029.GD4035307@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=paul@crapouillou.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