From: Jonathan Corbet <corbet@lwn.net>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Bumsik Kim <kbumsik@gmail.com>,
wim@linux-watchdog.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org, Bumsik Kim <k.bumsik@gmail.com>
Subject: Re: [PATCH] watchdog: clarify that stop() is optional
Date: Mon, 20 Apr 2020 17:12:08 -0600 [thread overview]
Message-ID: <20200420171208.3a2a5693@lwn.net> (raw)
In-Reply-To: <1fe9be6e-7da1-e738-c825-beddef31fd54@roeck-us.net>
On Thu, 2 Apr 2020 21:07:27 -0700
Guenter Roeck <linux@roeck-us.net> wrote:
> On 4/2/20 8:15 PM, Bumsik Kim wrote:
> > The commit d0684c8a9354 ("watchdog: Make stop function optional")
> > made stop function not mandatory, but the comments
> > and the doc weren't reflected. Fix it to clarify.
> >
> > Signed-off-by: Bumsik Kim <k.bumsik@gmail.com>
>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Applied, thanks.
jon
prev parent reply other threads:[~2020-04-20 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 3:15 [PATCH] watchdog: clarify that stop() is optional Bumsik Kim
2020-04-03 4:07 ` Guenter Roeck
2020-04-20 23:12 ` 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=20200420171208.3a2a5693@lwn.net \
--to=corbet@lwn.net \
--cc=k.bumsik@gmail.com \
--cc=kbumsik@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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).