From: Dmitry Safonov <dima@arista.com>
To: linux-kernel@vger.kernel.org
Cc: Dmitry Safonov <0x7f454c46@gmail.com>,
Dmitry Safonov <dima@arista.com>,
Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org
Subject: [PATCH 0/2] watchdog: Provide user control over WDOG_STOP_ON_REBOOT
Date: Thu, 13 Feb 2020 17:59:56 +0000 [thread overview]
Message-ID: <20200213175958.105914-1-dima@arista.com> (raw)
Add WDIOS_RUN_ON_REBOOT and WDIOS_STOP_ON_REBOOT to control the
watchdog's behavior over reboot.
Changes since RFC:
o rebase over v5.6
o fixed return code for ioctl()
I've sent RFC a while ago and it probably was very late in release
cycle to catch any attention:
https://lkml.kernel.org/r/20200121162145.166334-1-dima@arista.com
While waiting for rc1, I've changed my mind that it's RFC material and
sending it as PATCHv1 instead.
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>
Cc: linux-watchdog@vger.kernel.org
Dmitry Safonov (2):
watchdog: Check WDOG_STOP_ON_REBOOT in reboot notifier
watchdog/uapi: Add WDIOS_{RUN,STOP}_ON_REBOOT
drivers/watchdog/watchdog_core.c | 27 +++++++++++++--------------
drivers/watchdog/watchdog_dev.c | 12 ++++++++++++
include/linux/watchdog.h | 6 ++++++
include/uapi/linux/watchdog.h | 3 ++-
4 files changed, 33 insertions(+), 15 deletions(-)
--
2.25.0
next reply other threads:[~2020-02-13 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 17:59 Dmitry Safonov [this message]
2020-02-13 17:59 ` [PATCH 1/2] watchdog: Check WDOG_STOP_ON_REBOOT in reboot notifier Dmitry Safonov
2020-02-13 19:12 ` Guenter Roeck
2020-02-13 20:23 ` Dmitry Safonov
2020-02-13 17:59 ` [PATCH 2/2] watchdog/uapi: Add WDIOS_{RUN,STOP}_ON_REBOOT Dmitry Safonov
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=20200213175958.105914-1-dima@arista.com \
--to=dima@arista.com \
--cc=0x7f454c46@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).