From: Hemanth Selam <hemanth.selam@gmail.com>
To: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: [PATCH 1/2] watchdog: fix typos in comments
Date: Fri, 4 Sep 2026 17:07:40 +0530 [thread overview]
Message-ID: <20260904113744.19872-2-hemanth.selam@gmail.com> (raw)
In-Reply-To: <20260904113744.19872-1-hemanth.selam@gmail.com>
Fix typos in comments, reported by scripts/checkpatch.pl using the
misspelling list in scripts/spelling.txt. Only touches comments, no code
changes.
Assisted-by: Cursor:claude-opus-5
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
---
drivers/watchdog/davinci_wdt.c | 2 +-
drivers/watchdog/max63xx_wdt.c | 2 +-
drivers/watchdog/pcwd_pci.c | 2 +-
drivers/watchdog/pcwd_usb.c | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/watchdog/davinci_wdt.c b/drivers/watchdog/davinci_wdt.c
index 6ea0434f45c2..748dd24affb3 100644
--- a/drivers/watchdog/davinci_wdt.c
+++ b/drivers/watchdog/davinci_wdt.c
@@ -120,7 +120,7 @@ static unsigned int davinci_wdt_get_timeleft(struct watchdog_device *wdd)
u32 val;
struct davinci_wdt_device *davinci_wdt = watchdog_get_drvdata(wdd);
- /* if timeout has occured then return 0 */
+ /* if timeout has occurred then return 0 */
val = ioread32(davinci_wdt->base + WDTCR);
if (val & WDFLAG)
return 0;
diff --git a/drivers/watchdog/max63xx_wdt.c b/drivers/watchdog/max63xx_wdt.c
index e9073df1a7de..0aecf411f91b 100644
--- a/drivers/watchdog/max63xx_wdt.c
+++ b/drivers/watchdog/max63xx_wdt.c
@@ -64,7 +64,7 @@ struct max63xx_wdt {
* delay (selected with the "nodelay" parameter).
*
* I also decided to remove from the tables any timeout smaller than a
- * second, as it looked completly overkill...
+ * second, as it looked completely overkill...
*/
/* Timeouts in second */
diff --git a/drivers/watchdog/pcwd_pci.c b/drivers/watchdog/pcwd_pci.c
index a489b426f2ba..80fc4e6d3b0a 100644
--- a/drivers/watchdog/pcwd_pci.c
+++ b/drivers/watchdog/pcwd_pci.c
@@ -114,7 +114,7 @@ static unsigned long is_active;
static char expect_release;
/* this is private data for each PCI-PC watchdog card */
static struct {
- /* Wether or not the card has a temperature device */
+ /* Whether or not the card has a temperature device */
int supports_temp;
/* The card's boot status */
int boot_status;
diff --git a/drivers/watchdog/pcwd_usb.c b/drivers/watchdog/pcwd_usb.c
index d7c18c990649..b923fdaaa198 100644
--- a/drivers/watchdog/pcwd_usb.c
+++ b/drivers/watchdog/pcwd_usb.c
@@ -138,7 +138,7 @@ struct usb_pcwd_private {
/* true if we received a report after a command */
atomic_t cmd_received;
- /* Wether or not the device exists */
+ /* Whether or not the device exists */
int exists;
/* locks this structure */
struct mutex mtx;
--
2.48.1
next parent reply other threads:[~2026-09-04 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260904113744.19872-1-hemanth.selam@gmail.com>
2026-09-04 11:37 ` Hemanth Selam [this message]
2026-09-09 20:45 ` [PATCH 1/2] watchdog: fix typos in comments Guenter Roeck
2026-09-04 11:37 ` [PATCH 2/2] watchdog: fix repeated words " Hemanth Selam
2026-09-09 20:46 ` 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=20260904113744.19872-2-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.