From: Jonathan Corbet <corbet@lwn.net>
To: Guenter Roeck <linux@roeck-us.net>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/5] docs: watchdog: general cleaning and corrections
Date: Sun, 03 May 2026 09:20:05 -0600 [thread overview]
Message-ID: <87tssobjve.fsf@trenco.lwn.net> (raw)
In-Reply-To: <7a5971b2-e067-40cb-8d15-aaf1926af3c3@roeck-us.net>
Guenter Roeck <linux@roeck-us.net> writes:
> On 4/30/26 15:14, Randy Dunlap wrote:
>> Hi Wim,
>>
>> On 3/22/26 5:54 PM, Randy Dunlap wrote:
>>>
>>>
>>> On 3/3/26 9:23 AM, Jonathan Corbet wrote:
>>>> Randy Dunlap <rdunlap@infradead.org> writes:
>>>>
>>>>> Fix some obvious issues in the watchdog documentation files.
>>>>> I didn't try to fix every little niggling mistake.
>>>>>
>>>>> [PATCH 1/5] docs: watchdog: mlx-wdt: small fixes
>>>>> [PATCH 2/5] docs: watchdog: pcwd: fix typo and driver info.
>>>>> [PATCH 3/5] docs: watchdog-api: general cleaning
>>>>> [PATCH 4/5] docs: watchdog-kernel-api: general cleanups
>>>>> [PATCH 5/5] docs: watchdog-parameters: add missing watchdog_core parameters
>>>>>
>>>>> Documentation/watchdog/mlx-wdt.rst | 4 -
>>>>> Documentation/watchdog/pcwd-watchdog.rst | 19 +++++--
>>>>> Documentation/watchdog/watchdog-api.rst | 38 +++++++--------
>>>>> Documentation/watchdog/watchdog-kernel-api.rst | 20 +++++--
>>>>> Documentation/watchdog/watchdog-parameters.rst | 11 +++-
>>>>> 5 files changed, 58 insertions(+), 34 deletions(-)
>>>>
>>>> Wim, do you want to pick these up, or should I take them through the
>>>> docs tree?
>>>
>>> Wim, are you active? Can you reply and/or merge these?
>>
>> What's happening with these 5 patches?
>>
>
> It looks like Wim did not send a pull request for watchdog this time around/
> Wim, are you still active, or should I send pull requests going forward ?
OK, rather than let these languish further, I've just applied them.
Thanks,
jon
prev parent reply other threads:[~2026-05-03 15:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 1:03 [PATCH 0/5] docs: watchdog: general cleaning and corrections Randy Dunlap
2026-02-28 1:03 ` [PATCH 1/5] docs: watchdog: mlx-wdt: small fixes Randy Dunlap
2026-02-28 1:51 ` Guenter Roeck
2026-02-28 1:03 ` [PATCH 2/5] docs: watchdog: pcwd: fix typo and driver info Randy Dunlap
2026-02-28 1:51 ` Guenter Roeck
2026-02-28 1:04 ` [PATCH 3/5] docs: watchdog-api: general cleaning Randy Dunlap
2026-02-28 1:53 ` Guenter Roeck
2026-02-28 1:04 ` [PATCH 4/5] docs: watchdog-kernel-api: general cleanups Randy Dunlap
2026-02-28 1:55 ` Guenter Roeck
2026-02-28 1:04 ` [PATCH 5/5] docs: watchdog-parameters: add missing watchdog_core parameters Randy Dunlap
2026-02-28 1:54 ` Guenter Roeck
2026-03-03 17:23 ` [PATCH 0/5] docs: watchdog: general cleaning and corrections Jonathan Corbet
2026-03-23 0:54 ` Randy Dunlap
2026-04-30 22:14 ` Randy Dunlap
2026-04-30 23:21 ` Guenter Roeck
2026-05-03 15:20 ` Jonathan Corbet [this message]
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=87tssobjve.fsf@trenco.lwn.net \
--to=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=rdunlap@infradead.org \
--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