Linux Watchdog driver development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Philipp Hahn" <p.hahn@avm.de>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2 5/5] watchdog: Prefix WDT with ICS for clarity
Date: Mon, 04 May 2026 17:11:03 +0000	[thread overview]
Message-ID: <20260504171103.D3C5EC2BCB8@smtp.kernel.org> (raw)
In-Reply-To: <25e65a138f70239b6263bdfbed801f1acbb06688.1777902230.git.phahn-oss@avm.de>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Incomplete renaming: the 'ICS' prefix was not added to the Kconfig help text for the WDTPCI configuration.
--

commit 4485842d9f93fd889373b4245fc0ff5cb5d3e3b8
Author: Philipp Hahn <phahn-oss@avm.de>

watchdog: Prefix WDT with ICS for clarity

The commit updates documentation and Kconfig files to clarify that WDT refers
to the Watchdog timer from Industrial Computer Source (ICS). It adds the ICS
prefix in several places and includes a missing SPDX license identifier.

> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index dc78729ba2a5d..2cbf0391a065a 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
[ ... ]
> @@ -2270,10 +2270,10 @@ config MIXCOMWD
>  	  Most people will say N.
>  
>  config WDT
> -	tristate "WDT Watchdog timer"
> +	tristate "ICS WDT Watchdog timer"
>  	depends on ISA
>  	help
> -	  If you have a WDT500P or WDT501P watchdog board, say Y here,
> +	  If you have an ICS WDT500P or WDT501P watchdog board, say Y here,
>  	  otherwise N. It is not possible to probe for this board, which means
[ ... ]
> @@ -2304,7 +2304,7 @@ config PCIPCWATCHDOG
>  	  Most people will say N.
>  
>  config WDTPCI
> -	tristate "PCI-WDT500/501 Watchdog timer"
> +	tristate "ICS PCI-WDT500/501 Watchdog timer"
>  	depends on PCI && HAS_IOPORT
>  	help
>  	  If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.

This isn't a bug, but should the help text for WDTPCI also be updated to
include the ICS prefix for consistency? The WDT config help text was updated
above, but this description still reads "If you have a PCI-WDT500/501
watchdog board".

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1777902230.git.phahn-oss@avm.de?part=5

  reply	other threads:[~2026-05-04 17:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04 11:02 [PATCH 0/6] Cleanup Linux Watchdog documentation Philipp Hahn
2026-05-04 11:02 ` [PATCH 1/6] watchdog: Fix wrong SPDX license identifier Philipp Hahn
2026-05-04 11:17   ` sashiko-bot
2026-05-04 13:44     ` Guenter Roeck
2026-05-04 13:52       ` AW: " Philipp Hahn
2026-05-04 14:07         ` Guenter Roeck
2026-05-04 11:02 ` [PATCH 2/6] watchdog: Change suffix .txt to .rst in references Philipp Hahn
2026-05-04 11:02 ` [PATCH 3/6] watchdog: Move `struct` before name Philipp Hahn
2026-05-04 11:02 ` [PATCH 4/6] watchdog: Replace intermixed tab/space indent Philipp Hahn
2026-05-04 11:02 ` [PATCH 5/6] watchdog: Separate kind of documentation Philipp Hahn
2026-05-04 11:02 ` [PATCH 6/6] watchdog: Prefix WDT with ICS for clarity Philipp Hahn
2026-05-04 14:00   ` Guenter Roeck
2026-05-04 13:49 ` [PATCH v2 0/5] Cleanup Linux Watchdog documentation Philipp Hahn
2026-05-04 13:49   ` [PATCH v2 1/5] watchdog: Change suffix .txt to .rst in references Philipp Hahn
2026-05-04 13:50   ` [PATCH v2 2/5] watchdog: Move `struct` before name Philipp Hahn
2026-05-04 13:50   ` [PATCH v2 3/5] watchdog: Replace intermixed tab/space indent Philipp Hahn
2026-05-04 13:50   ` [PATCH v2 4/5] watchdog: Separate kind of documentation Philipp Hahn
2026-05-04 13:50   ` [PATCH v2 5/5] watchdog: Prefix WDT with ICS for clarity Philipp Hahn
2026-05-04 17:11     ` sashiko-bot [this message]
2026-05-04 14:11   ` [PATCH v2 0/5] Cleanup Linux Watchdog documentation 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=20260504171103.D3C5EC2BCB8@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=p.hahn@avm.de \
    --cc=sashiko@lists.linux.dev \
    /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