From: Randy Dunlap <rdunlap@infradead.org>
To: Wang Zihan <3772548978@qq.com>, linux-watchdog@vger.kernel.org
Cc: wim@linux-watchdog.org, linux@roeck-us.net, corbet@lwn.net,
skhan@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: watchdog: Fix typo "oncse" -> "once"
Date: Sat, 2 May 2026 09:48:26 -0700 [thread overview]
Message-ID: <563f2633-4304-45fb-9188-1b5235463181@infradead.org> (raw)
In-Reply-To: <9a6393f4-6aec-4f64-b3ef-9566206c4ac7@infradead.org>
On 5/2/26 9:32 AM, Randy Dunlap wrote:
>
>
> On 5/2/26 4:19 AM, Wang Zihan wrote:
>> Fix a typo in mlx-wdt.rst documentation.
>>
>> Signed-off-by: Wang Zihan <3772548978@qq.com>
>> ---
>> Documentation/watchdog/mlx-wdt.rst | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/watchdog/mlx-wdt.rst b/Documentation/watchdog/mlx-wdt.rst
>> index 35e690dea..3778f85d1 100644
>> --- a/Documentation/watchdog/mlx-wdt.rst
>> +++ b/Documentation/watchdog/mlx-wdt.rst
>> @@ -48,7 +48,7 @@ which is optional.
>> Watchdog can be started during a probe, in this case it will be
>> pinged by watchdog core before watchdog device will be opened by
>> user space application.
>> -Watchdog can be initialised in nowayout way, i.e. oncse started
>> +Watchdog can be initialised in nowayout way, i.e. once started
>> it can't be stopped.
>>
>> This mlx-wdt driver supports both HW watchdog implementations.
>
> This typo is also fixed in my 5-patch series (pending).
[PATCH 1/5] docs: watchdog: mlx-wdt: small fixes
https://lore.kernel.org/linux-watchdog/20260228010402.2389343-2-rdunlap@infradead.org/
--
~Randy
next prev parent reply other threads:[~2026-05-02 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 11:19 [PATCH] Documentation: watchdog: Fix typo "oncse" -> "once" Wang Zihan
2026-05-02 14:49 ` Guenter Roeck
2026-05-02 16:32 ` Randy Dunlap
2026-05-02 16:48 ` Randy Dunlap [this message]
2026-05-03 15:21 ` Jonathan Corbet
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=563f2633-4304-45fb-9188-1b5235463181@infradead.org \
--to=rdunlap@infradead.org \
--cc=3772548978@qq.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=skhan@linuxfoundation.org \
--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