linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Sangjung Woo <sangjung.woo@samsung.com>,
	Wim Van Sebroeck <wim@iguana.be>
Cc: Guenter Roeck <linux@roeck-us.net>,
	linux-watchdog@vger.kernel.org, trivial@kernel.org,
	linux-kernel@vger.kernel.org, again4you@gmail.com
Subject: Re: [PATCH v2] Documentation: fix two typos in watchdog-api.txt
Date: Wed, 30 Jul 2014 00:22:39 -0700	[thread overview]
Message-ID: <53D89D3F.8000309@infradead.org> (raw)
In-Reply-To: <1406681781-3533-1-git-send-email-sangjung.woo@samsung.com>

On 07/29/14 17:56, Sangjung Woo wrote:
> This patch changes 'go of' to 'go off' and 'pretimout' to
> 'pretimeout'.
> 
> Signed-off-by: Sangjung Woo <sangjung.woo@samsung.com>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>

Acked-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

> ---
>  Documentation/watchdog/watchdog-api.txt |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/watchdog/watchdog-api.txt b/Documentation/watchdog/watchdog-api.txt
> index eb7132e..b3a701f 100644
> --- a/Documentation/watchdog/watchdog-api.txt
> +++ b/Documentation/watchdog/watchdog-api.txt
> @@ -118,7 +118,7 @@ resets.
>  Note that the pretimeout is the number of seconds before the time
>  when the timeout will go off.  It is not the number of seconds until
>  the pretimeout.  So, for instance, if you set the timeout to 60 seconds
> -and the pretimeout to 10 seconds, the pretimout will go of in 50
> +and the pretimeout to 10 seconds, the pretimeout will go off in 50
>  seconds.  Setting a pretimeout to zero disables it.
>  
>  There is also a get function for getting the pretimeout:
> 


-- 
~Randy

      reply	other threads:[~2014-07-30  7:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30  0:56 [PATCH v2] Documentation: fix two typos in watchdog-api.txt Sangjung Woo
2014-07-30  7:22 ` Randy Dunlap [this message]

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=53D89D3F.8000309@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=again4you@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=sangjung.woo@samsung.com \
    --cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).