From: Sander Vanheule <sander@svanheule.net>
To: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: Rustam Adilov <adilov@disroot.org>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
Sander Vanheule <sander@svanheule.net>
Subject: [PATCH 0/2] watchdog: realtek-otto: various fixes
Date: Fri, 15 May 2026 23:23:49 +0200 [thread overview]
Message-ID: <20260515212351.752054-1-sander@svanheule.net> (raw)
These patches fix some minor issues with the current code, as reported
in [1]. The individual patches can be applied in any order.
Should I add a Reported-by for the Sashiko review, or how should this be
handled?
[1] https://patch.msgid.link/20260509172748.54B33C2BCB2@smtp.kernel.org/
Sander Vanheule (2):
watchdog: realtek-otto: prevent PHASE2 underflows
watchdog: realtek-otto: enable clock before using I/O
drivers/watchdog/realtek_otto_wdt.c | 20 +++++++-------------
1 file changed, 7 insertions(+), 13 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-15 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 21:23 Sander Vanheule [this message]
2026-05-15 21:23 ` [PATCH 1/2] watchdog: realtek-otto: prevent PHASE2 underflows Sander Vanheule
2026-05-15 21:23 ` [PATCH 2/2] watchdog: realtek-otto: enable clock before using I/O Sander Vanheule
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=20260515212351.752054-1-sander@svanheule.net \
--to=sander@svanheule.net \
--cc=adilov@disroot.org \
--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