From: Guenter Roeck <linux@roeck-us.net>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: Implement status function in watchdog core
Date: Sun, 17 Jul 2016 13:11:13 -0700 [thread overview]
Message-ID: <578BE661.9080709@roeck-us.net> (raw)
In-Reply-To: <20160717195916.GD32751@spo001.leaseweb.nl>
Hi Wim,
On 07/17/2016 12:59 PM, Wim Van Sebroeck wrote:
> Hi Guenter,
>
> I didn't find the following patches that are in your tree in my e-mail:
> watchdog: Improve description of min_hw_heartbeat_ms
> watchdog: Implement status function in watchdog core
> watchdog: sbsa: Drop status function
> watchdog: tangox: Mark running watchdog correctly
> watchdog: Eliminate status callback
>
Interesting. I checked my logs ... looks like I never sent those to the list. Oops :-(. Sorry for that; I thought I did.
> I added "watchdog: Improve description of min_hw_heartbeat_ms" and "watchdog: tangox: Mark running watchdog correctly" to the linux-watchdog-next tree.
>
Great, thanks!
> I didn't add the status function implementation. The reason is because there are cards that have means to read certain info life (like pcwd cards and the wdt cards). The implementation doesn't foresee this functionality and thus should be corrected first. (for these cards you want to call the status functions of these cards).
Ok, thanks for letting me know. I'll have another look.
What would be the best approach to use for those drivers ? Overlay the data
from the driver with the data from the watchdog core, or completely rely
on the data from the driver ?
Thanks,
Guenter
next prev parent reply other threads:[~2016-07-17 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 19:59 Implement status function in watchdog core Wim Van Sebroeck
2016-07-17 20:11 ` Guenter Roeck [this message]
2016-07-17 20:14 ` Wim Van Sebroeck
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=578BE661.9080709@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-watchdog@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.