On 05/19/2015 01:26 AM, Timo Kokkonen wrote:
Before extending the watchdog core midlayer, it is useful to rename the watchdog_active function so that it states explicitly what it really does. That is, "active" watchdog means really that the watchdog hardware is running and needs pinging to prevent a watchdog reset taking place in near future. This is different to "watchdog open" state, which simply states that kernel is expecting the user space to keep the watchdog alive. These states might become different mainly because some hardware have limitations that prevent them from being stopped at will.
I don't see why this is needed. If you need another state, per your description, it would be "open" in addition to "active". Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
