[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <565341F6.8040604@roeck-us.net>
Date: Mon, 23 Nov 2015 08:42:30 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Alexander Stein <alexander.stein@...tec-electronic.com>,
linux-kernel@...r.kernel.org
Cc: linux-watchdog@...r.kernel.org, Wim Van Sebroeck <wim@...ana.be>,
Timo Kokkonen <timo.kokkonen@...code.fi>,
Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
linux-doc@...r.kernel.org, Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH v5 2/8] watchdog: Introduce WDOG_RUNNING flag
On 11/23/2015 08:30 AM, Alexander Stein wrote:
> On Sunday 22 November 2015 19:20:59, Guenter Roeck wrote:
>> diff --git a/Documentation/watchdog/watchdog-kernel-api.txt b/Documentation/watchdog/watchdog-kernel-api.txt
>> index f66859117d1f..3f0963b2c33e 100644
>> --- a/Documentation/watchdog/watchdog-kernel-api.txt
>> +++ b/Documentation/watchdog/watchdog-kernel-api.txt
>> @@ -212,6 +212,14 @@ bit-operations. The status bits that are defined are:
>> any watchdog_ops, so that you can be sure that no operations (other then
>> unref) will get called after unregister, even if userspace still holds a
>> reference to /dev/watchdog
>> +* WDOG_RUNNING: Set by the watchdog driver if the hardware watchdog is running.
>> + The bit must be set if the watchdog timer hardware can not be stopped.
>> + The bit may also be set if the watchdog timer is running aftyer booting,
> ^
> typo
Thanks, fixed.
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists