From: Zoe Gates <zoe.blair.gates@icloud.com>
To: hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
borntraeger@linux.ibm.com, svens@linux.ibm.com,
wim@linux-watchdog.org, linux@roeck-us.net,
linux-s390@vger.kernel.org, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] watchdog/diag288: Fix module comment typos
Date: Mon, 27 Oct 2025 23:01:49 -0500 [thread overview]
Message-ID: <fe09cb336dca5f277769b115dae55b9639dc92a7.camel@icloud.com> (raw)
From ebec904b22077c3ebd0a18956397a9b0540a2714 Mon Sep 17 00:00:00 2001
From: Zoe Gates <zoe@zeocities.dev>
Date: Mon, 27 Oct 2025 22:14:50 -0500
Subject: [PATCH 2/3] watchdog/diag288: Fix module comment typos
Correct spelling and capitalizaion in the header comment so the
documentation reads cleanly.
Signed-off-by: Zoe Gates <zoe@zeocities.dev>
---
drivers/watchdog/diag288_wdt.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/watchdog/diag288_wdt.c
b/drivers/watchdog/diag288_wdt.c
index 887d5a6c155b..656b937f7653 100644
--- a/drivers/watchdog/diag288_wdt.c
+++ b/drivers/watchdog/diag288_wdt.c
@@ -6,10 +6,10 @@
* to CP.
*
* The command can be altered using the module parameter "cmd". This
is
- * not recommended because it's only supported on z/VM but not whith
LPAR.
+ * not recommended because it's only supported on z/VM but not with
LPAR.
*
- * On LPAR, the watchdog will always trigger a system restart. the
module
- * paramter cmd is meaningless here.
+ * On LPAR, the watchdog will always trigger a system restart. The
module
+ * parameter cmd is meaningless here.
*
*
* Copyright IBM Corp. 2004, 2013
--
2.51.1
next reply other threads:[~2025-10-28 4:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 4:01 Zoe Gates [this message]
2025-11-02 23:05 ` [PATCH 2/3] watchdog/diag288: Fix module comment typos 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=fe09cb336dca5f277769b115dae55b9639dc92a7.camel@icloud.com \
--to=zoe.blair.gates@icloud.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=svens@linux.ibm.com \
--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).