From: Guenter Roeck <linux@roeck-us.net>
To: Sunny Patel <nueralspacetech@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
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: Fri, 10 Apr 2026 08:19:25 -0700 [thread overview]
Message-ID: <fe3de980-e918-47ae-862a-969a5b117ae0@roeck-us.net> (raw)
In-Reply-To: <20260410072825.19114-1-nueralspacetech@gmail.com>
On Fri, Apr 10, 2026 at 12:58:11PM +0530, Sunny Patel wrote:
> Good Point. So again revisited the watchdog core
> api and list out the deprecated one and marked
> as deprecated in doc and also mentioned it just
> for legacy driver and not for newer one.
>
> As someof the legacy driver still have reference
> to old api so just marked as deprecated in doc.
>
> Also checked with other watchdog related api
> which are deprecated in driver but still present
> in doc but didn't find any.
>
> ---
The above would show up as commit message, there is no change log, and
this e-mail was sent as response to v1. And I can see that without even
looking at the patch itself.
That makes me wonder what Documentation/process/submitting-patches.rst
is useful for. No one seems to bother reading it. We might as well
just remove it.
Guenter
next prev parent reply other threads:[~2026-04-10 15:19 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 [this message]
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
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=fe3de980-e918-47ae-862a-969a5b117ae0@roeck-us.net \
--to=linux@roeck-us.net \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--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®