From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-watchdog@vger.kernel.org, Wim Van Sebroeck <wim@iguana.be>,
linux-kernel@vger.kernel.org,
Timo Kokkonen <timo.kokkonen@offcode.fi>,
linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v4 1/9] watchdog: Always evaluate new timeout against min_timeout
Date: Tue, 29 Sep 2015 10:51:02 +0200 [thread overview]
Message-ID: <20150929085102.GB3982@pengutronix.de> (raw)
In-Reply-To: <1443515252-30085-2-git-send-email-linux@roeck-us.net>
On Tue, Sep 29, 2015 at 01:27:24AM -0700, Guenter Roeck wrote:
> Up to now, a new timeout value is only evaluated against min_timeout
> if max_timeout is provided. This does not really make sense; a driver
> can have a minimum timeout even if it does not have a maximum timeout.
> Ensure that it is not smaller than min_timeout, even if max_timeout
> is not set.
>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2015-09-29 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 8:27 [PATCH v4 0/9] watchdog: Add support for keepalives triggered by infrastructure Guenter Roeck
2015-09-29 8:27 ` [PATCH v4 1/9] watchdog: Always evaluate new timeout against min_timeout Guenter Roeck
2015-09-29 8:51 ` Uwe Kleine-König [this message]
2015-09-29 8:27 ` [PATCH v4 2/9] watchdog: watchdog_dev: Use single variable name for struct watchdog_device Guenter Roeck
2015-09-29 8:27 ` [PATCH v4 3/9] watchdog: Introduce hardware maximum timeout in watchdog core Guenter Roeck
2015-09-29 8:27 ` [PATCH v4 4/9] watchdog: Introduce WDOG_RUNNING flag Guenter Roeck
2015-09-29 8:27 ` [PATCH v4 5/9] watchdog: Make set_timeout function optional Guenter Roeck
2015-09-29 8:27 ` [PATCH v4 6/9] watchdog: imx2: Convert to use infrastructure triggered keepalives Guenter Roeck
2015-09-29 8:27 ` [PATCH v4 7/9] watchdog: retu: " Guenter Roeck
2015-09-29 8:27 ` [PATCH v4 8/9] watchdog: at91sam9: " Guenter Roeck
2015-09-29 8:27 ` [PATCH v4 9/9] watchdog: Add support for minimum time between heartbeats Guenter Roeck
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=20150929085102.GB3982@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=timo.kokkonen@offcode.fi \
--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®