From: Guenter Roeck <linux@roeck-us.net>
To: William Breathitt Gray <vilhelm.gray@gmail.com>, wim@iguana.be
Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7] watchdog: Add watchdog timer support for the WinSystems EBC-C384
Date: Sun, 28 Feb 2016 20:40:48 -0800 [thread overview]
Message-ID: <56D3CBD0.1000706@roeck-us.net> (raw)
In-Reply-To: <20160229042039.GA29582@sophia>
Hi,
On 02/28/2016 08:20 PM, William Breathitt Gray wrote:
> The WinSystems EBC-C384 has an onboard watchdog timer. The timeout range
> supported by the watchdog timer is 1 second to 255 minutes. Timeouts
> under 256 seconds have a 1 second granularity, while the rest have a 1
> minute granularity.
>
> This driver adds watchdog timer support for this onboard watchdog timer.
> The timeout may be configured via the timeout module parameter.
>
> Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> Changes in v7:
> - Make sure timeout member is in seconds resolution despite minutes
> granularity
>
For Wim's benefit:
You forgot the actual change. The follow-up RESEND is really confusing;
RESEND indicates that no change was made, and leaves it up to us to figure
out what is going on. If something like this happens again, just add
another rev and add a note indicating what has (really) changed.
Also, when you make code changes, please drop previous Reviewed-by: or
Acked-by: tags unless you got explicit permission from the reviewer
to keep the tag.
Thanks,
Guenter
prev parent reply other threads:[~2016-02-29 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 4:20 [PATCH v7] watchdog: Add watchdog timer support for the WinSystems EBC-C384 William Breathitt Gray
2016-02-29 4:26 ` William Breathitt Gray
2016-02-29 4:40 ` Guenter Roeck [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=56D3CBD0.1000706@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