From: Randy Dunlap <rdunlap@infradead.org>
To: Sunny Patel <nueralspacetech@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-watchdog@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: Refactored watchdog old doc
Date: Sat, 11 Apr 2026 10:22:42 -0700 [thread overview]
Message-ID: <303dcd9e-ca40-48b7-851e-6cd283cb96ad@infradead.org> (raw)
In-Reply-To: <20260411150922.20536-1-nueralspacetech@gmail.com>
On 4/11/26 8:09 AM, Sunny Patel wrote:
> Mark WDIOC_GETTEMP and WDIOS_TEMPPANIC as deprecated since
> neither is implemented by the watchdog core and both are only
> present in a small number of legacy drivers.
>
> Add documentation for previously undocumented status bits
> WDIOF_MAGICCLOSE and WDIOF_ALARMONLY in the options field.
>
> Add documentation for WDIOF_PRETIMEOUT and WDIOF_SETTIMEOUT
> status bits describing their respective ioctls.
>
> Fix the following issues in existing documentation:
> - Remove version-specific reference to Linux 2.4.18 from
> the GETTIMEOUT ioctl description
> - Fix duplicate "was is" in printf format strings
> - Replace [FIXME] placeholder with proper descriptions for
> WDIOS_DISABLECARD, WDIOS_ENABLECARD and WDIOS_TEMPPANIC
>
> Signed-off-by: Sunny Patel <nueralspacetech@gmail.com>
> ---
>
> Changes in v2:
> - Fixed typos: "tiemout" -> "timeout", "characted" -> "character"
> - Fixed "small number if legacy" -> "of legacy"
> - Fixed capitalization: "New Drivers" -> "New drivers", "USE" -> "Use"
> - Fixed spacing: "WDIOS_DISABLECARD,this" -> "WDIOS_DISABLECARD, this"
> - Fixed double spaces in two places
> - Added missing newline at end of file
> - Rewrote commit message
However, you failed to fix a malformed table warning that I reported here:
https://lore.kernel.org/linux-doc/9e3403a0-4ec2-4fbe-a50f-53f939c1d841@infradead.org/
Documentation/watchdog/watchdog-api.rst:250: ERROR: Malformed table.
Text in column margin in table line 2.
================ ================================
WDIOF_ALARMONLY Not a reboot watchdog
================ ================================
So I repeat, please test your patches.
>
> Documentation/watchdog/watchdog-api.rst | 59 +++++++++++++++++++++----
> 1 file changed, 51 insertions(+), 8 deletions(-)
--
~Randy
next prev parent reply other threads:[~2026-04-11 17:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 17:53 [PATCH] " Sunny Patel
2026-04-10 0:31 ` Randy Dunlap
2026-04-10 0:53 ` Guenter Roeck
2026-04-10 7:28 ` [PATCH v2] " Sunny Patel
2026-04-10 15:19 ` Guenter Roeck
2026-04-10 16:45 ` Jonathan Corbet
2026-04-10 17:27 ` Guenter Roeck
2026-04-11 15:09 ` Sunny Patel
2026-04-11 17:22 ` Randy Dunlap [this message]
2026-04-11 19:07 ` Guenter Roeck
2026-04-12 0:09 ` Guenter Roeck
2026-04-12 8:22 ` [PATCH v3] " Sunny Patel
2026-04-10 7:15 [PATCH v2] " Sunny Patel
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=303dcd9e-ca40-48b7-851e-6cd283cb96ad@infradead.org \
--to=rdunlap@infradead.org \
--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=nueralspacetech@gmail.com \
--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
all inboxes | Powered by JetHome®