From: Guenter Roeck <linux@roeck-us.net>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: wim@iguana.be, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Add ebc-c384_wdt watchdog-parameters.txt entry
Date: Wed, 11 May 2016 07:19:51 -0700 [thread overview]
Message-ID: <20160511141951.GB8192@roeck-us.net> (raw)
In-Reply-To: <20160511124746.GA5314@sophia>
On Wed, May 11, 2016 at 08:47:46AM -0400, William Breathitt Gray wrote:
> The WinSystems EBC-C384 watchdog timer driver supports two module
> parameters: timeout and nowayout. These parameters should be documented
> in the watchdog-parameters.txt file.
>
> Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> Documentation/watchdog/watchdog-parameters.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/watchdog/watchdog-parameters.txt b/Documentation/watchdog/watchdog-parameters.txt
> index c161399..a8d3642 100644
> --- a/Documentation/watchdog/watchdog-parameters.txt
> +++ b/Documentation/watchdog/watchdog-parameters.txt
> @@ -86,6 +86,10 @@ nowayout: Watchdog cannot be stopped once started
> davinci_wdt:
> heartbeat: Watchdog heartbeat period in seconds from 1 to 600, default 60
> -------------------------------------------------
> +ebc-c384_wdt:
> +timeout: Watchdog timeout in seconds. (1<=timeout<=15300, default=60)
> +nowayout: Watchdog cannot be stopped once started
> +-------------------------------------------------
> ep93xx_wdt:
> nowayout: Watchdog cannot be stopped once started
> timeout: Watchdog timeout in seconds. (1<=timeout<=3600, default=TBD)
> --
> 2.7.3
>
next prev parent reply other threads:[~2016-05-11 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 12:47 William Breathitt Gray
2016-05-11 14:19 ` Guenter Roeck [this message]
2016-05-14 18:35 ` 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=20160511141951.GB8192@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=vilhelm.gray@gmail.com \
--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
all inboxes | Powered by JetHome®