From: Radu Rendec <rrendec@arista.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wim Van Sebroeck <wim@iguana.be>, linux-watchdog@vger.kernel.org
Subject: [PATCH 0/2] xen_wdt: use the watchdog subsystem
Date: Fri, 3 Nov 2017 15:31:51 +0000 [thread overview]
Message-ID: <20171103153153.9992-1-rrendec@arista.com> (raw)
Hi Guenter,
I just figured out we have a similar use case (of two watchdogs at the
same time) that involves the xen_wdt driver. I thought "same problem,
same fix", so I decided to port xen_wdt to use the watchdog subsystem.
This patch series contains similar changes to what I have recently done
for i6300esb. The changes are simpler though, because the Xen hypervisor
cannot expose multiple watchdogs to the guest, and so the driver doesn't
need to allocate watchdog structures dynamically.
I tried to avoid all the problems I had with the i6300esb patches and
hopefully these new patches don't have as many issues (or none at all).
Thanks,
Radu
Radu Rendec (2):
watchdog: xen_wdt: use the watchdog subsystem
watchdog: xen_wdt: remove info message and version number
drivers/watchdog/xen_wdt.c | 208 +++++++++------------------------------------
1 file changed, 38 insertions(+), 170 deletions(-)
--
2.13.6
next reply other threads:[~2017-11-03 15:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 15:31 Radu Rendec [this message]
2017-11-03 15:31 ` [PATCH 1/2] watchdog: xen_wdt: use the watchdog subsystem Radu Rendec
2017-11-05 15:35 ` [1/2] " Guenter Roeck
2017-11-03 15:31 ` [PATCH 2/2] watchdog: xen_wdt: remove info message and version number Radu Rendec
2017-11-05 15:39 ` [2/2] " Guenter Roeck
2017-11-06 17:39 ` Radu Rendec
2017-11-06 18:04 ` Guenter Roeck
2017-11-06 19:04 ` [PATCH v2 0/2] xen_wdt: use the watchdog subsystem Radu Rendec
2017-11-06 19:04 ` [PATCH v2 1/2] watchdog: " Radu Rendec
2017-11-11 16:40 ` [v2,1/2] " Guenter Roeck
2017-11-14 15:05 ` Radu Rendec
2017-11-06 19:04 ` [PATCH v2 2/2] watchdog: xen_wdt: remove info message and version number Radu Rendec
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=20171103153153.9992-1-rrendec@arista.com \
--to=rrendec@arista.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@iguana.be \
/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