Linux Watchdog driver development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Triet Hoang" <triet.hoang.dev@gmail.com>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2 3/8] watchdog: keembay_wdt: Convert to DEFINE_SIMPLE_DEV_PM_OPS()
Date: Mon, 14 Sep 2026 09:11:55 +0000	[thread overview]
Message-ID: <20260914091155.EC2C21F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260914085451.891675-4-triet.hoang.dev@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch uses `pm_sleep_ptr()` for the `dev_pm_ops` structure pointer, which contradicts the commit message and violates PM subsystem guidelines.
--

commit c35ef6ee0f1ec7517f550f44b58852af01504c3c
Author: Triet Hoang <triet.hoang.dev@gmail.com>

watchdog: keembay_wdt: Convert to DEFINE_SIMPLE_DEV_PM_OPS()

This commit updates the keembay_wdt driver to use DEFINE_SIMPLE_DEV_PM_OPS(),
allowing the removal of the __maybe_unused annotations on the suspend and
resume callbacks. It also aims to assign the operations using the updated
power management pointer macros.

> diff --git a/drivers/watchdog/keembay_wdt.c b/drivers/watchdog/keembay_wdt.c
> index 7c8e53921e407..2c187b20a5ec1 100644
> --- a/drivers/watchdog/keembay_wdt.c
> +++ b/drivers/watchdog/keembay_wdt.c
[ ... ]
> @@ -284,7 +283,7 @@ static struct platform_driver keembay_wdt_driver = {
>  	.driver	= {
>  		.name		= "keembay_wdt",
>  		.of_match_table	= keembay_wdt_match,
> -		.pm		= &keembay_wdt_pm_ops,
> +		.pm		= pm_sleep_ptr(&keembay_wdt_pm_ops),
>  	},
>  };

[Severity: Medium]
The commit message mentions converting to pm_ptr(), but pm_sleep_ptr() is
used here for the dev_pm_ops structure pointer in keembay_wdt_driver.

According to the power management subsystem guidelines, pm_sleep_ptr()
should be used for individual sleep callbacks, while pm_ptr() should be
used for the dev_pm_ops structure pointer itself. Should this be updated
to use pm_ptr() to match both the subsystem guidelines and the stated
intent in the commit message?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260914085451.891675-1-triet.hoang.dev@gmail.com?part=3

  reply	other threads:[~2026-09-14  9:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14  8:54 [PATCH v2 0/8] watchdog: Convert drivers to DEFINE_SIMPLE_DEV_PM_OPS() Triet Hoang
2026-09-14  8:54 ` [PATCH v2 1/8] watchdog: cadence_wdt: Convert " Triet Hoang
2026-09-16  3:28   ` Tzung-Bi Shih
2026-09-16  4:54     ` Triet Hoang
2026-09-14  8:54 ` [PATCH v2 2/8] watchdog: da9062: " Triet Hoang
2026-09-14  8:54 ` [PATCH v2 3/8] watchdog: keembay_wdt: " Triet Hoang
2026-09-14  9:11   ` sashiko-bot [this message]
2026-09-14  9:21   ` Triet Hoang
2026-09-14  8:54 ` [PATCH v2 4/8] watchdog: msc313e_wdt: " Triet Hoang
2026-09-14  9:20   ` sashiko-bot
2026-09-16  3:35     ` Tzung-Bi Shih
2026-09-14  8:54 ` [PATCH v2 5/8] watchdog: of_xilinx_wdt: " Triet Hoang
2026-09-14  8:54 ` [PATCH v2 6/8] watchdog: pm8916_wdt: " Triet Hoang
2026-09-14  9:33   ` sashiko-bot
2026-09-14  8:54 ` [PATCH v2 7/8] watchdog: sp805_wdt: " Triet Hoang
2026-09-14  8:54 ` [PATCH v2 8/8] watchdog: stmp3xxx_rtc_wdt: " Triet Hoang

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=20260914091155.EC2C21F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=triet.hoang.dev@gmail.com \
    /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