From: Sangjung <sangjung.woo@samsung.com>
To: Randy Dunlap <rdunlap@infradead.org>, Wim Van Sebroeck <wim@iguana.be>
Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
again4you@gmail.com, Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH] Documentation: fix a typo in watchdog-api.txt
Date: Wed, 30 Jul 2014 10:03:36 +0900 [thread overview]
Message-ID: <53D84468.6070001@samsung.com> (raw)
In-Reply-To: <53D7D02D.6010508@infradead.org>
On 07/30/2014 01:47 AM, Randy Dunlap wrote:
> On 07/29/14 01:04, Sangjung Woo wrote:
>> Signed-off-by: Sangjung Woo <sangjung.woo@samsung.com>
>> ---
>> 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..53c49a4 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 pretimout will go off in 50
> pretimeout
>
> Please correct that word also and then resend. Also resend to:
> trivial@kernel.org
>
> Thanks.
I resent it after modification.
Thanks for your opinion.
Best regards,
Sangjung
>
>> seconds. Setting a pretimeout to zero disables it.
>>
>> There is also a get function for getting the pretimeout:
>>
>
prev parent reply other threads:[~2014-07-30 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 8:04 [PATCH] Documentation: fix a typo in watchdog-api.txt Sangjung Woo
2014-07-29 14:11 ` Guenter Roeck
2014-07-29 16:47 ` Randy Dunlap
2014-07-29 20:54 ` Wim Van Sebroeck
2014-07-29 22:36 ` Randy Dunlap
2014-07-30 1:03 ` Sangjung [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=53D84468.6070001@samsung.com \
--to=sangjung.woo@samsung.com \
--cc=again4you@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=rdunlap@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.