On 22 May 2017 at 16:06, Rasmus Villemoes wrote:
>
> Rasmus Villemoes (3):
> watchdog: introduce watchdog_worker_should_ping helper
> watchdog: introduce watchdog.open_timeout commandline parameter
> watchdog: introduce CONFIG_WATCHDOG_OPEN_TIMEOUT
>
> Documentation/watchdog/watchdog-parame
On 2017-05-22 20:07, Alan Cox wrote:
> On Mon, 22 May 2017 16:06:36 +0200
> Rasmus Villemoes wrote:
>
>> If a watchdog driver tells the framework that the device is running,
>> the framework takes care of feeding the watchdog until userspace opens
>> the device. If the userspace application which
On Mon, May 22, 2017 at 07:07:51PM +0100, Alan Cox wrote:
> On Mon, 22 May 2017 16:06:36 +0200
> Rasmus Villemoes wrote:
>
> > If a watchdog driver tells the framework that the device is running,
> > the framework takes care of feeding the watchdog until userspace opens
> > the device. If the use
On Mon, 22 May 2017 16:06:36 +0200
Rasmus Villemoes wrote:
> If a watchdog driver tells the framework that the device is running,
> the framework takes care of feeding the watchdog until userspace opens
> the device. If the userspace application which is supposed to do that
> never comes up prope
If a watchdog driver tells the framework that the device is running,
the framework takes care of feeding the watchdog until userspace opens
the device. If the userspace application which is supposed to do that
never comes up properly, the watchdog is fed indefinitely by the
kernel. This can be espe
