From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Guenter Roeck <patchwork@patchwork.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, Doug Anderson <dianders@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v7 0/9] watchdog: Add support for keepalives triggered by infrastructure
Date: Tue, 26 Jan 2016 09:09:04 +0100 [thread overview]
Message-ID: <20160126080904.GV3338@pengutronix.de> (raw)
In-Reply-To: <1453776796-3885-1-git-send-email-patchwork@patchwork.roeck-us.net>
Hello Guenter,
On Mon, Jan 25, 2016 at 06:53:07PM -0800, Guenter Roeck wrote:
> Patch #1 adds timer functionality to the watchdog core. It solves the problem
> of short maximum hardware timeouts by augmenting heartbeats triggered from
> user space with internally triggered heartbeats.
>
> Patch #2 adds functionality to generate heartbeats while the watchdog device
> is closed. It handles situation where where the watchdog is running after
> the driver has been instantiated, but the device is not yet opened,
> and post-close situations necessary if a watchdog can not be stopped.
>
> Patch #3 makes the set_timeout function optional. This is now possible since
> timeout changes can now be completely handled in the watchdog core, for
> example if the hardware watchdog timeout is fixed.
>
> Patch #4 adds code to ensure that the minimum time between heartbeats meets
> constraints provided by the watchdog driver.
>
> Patch #5 simplifies the watchdog_update_worker() function introduced with
> patch #1 to only take a single argument, and to always cancel any pending
> work if a worker is not or no longer needed. This patch is kept as separate
> patch on purpose, to enable dropping or reverting it easily if it causes
> any problems. It should not cause any problems; this is just out of an
> abundance of caution.
Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> for patches
1-5.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2016-01-26 8:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 2:53 [PATCH v7 0/9] watchdog: Add support for keepalives triggered by infrastructure Guenter Roeck
2016-01-26 2:53 ` [PATCH v7 1/9] watchdog: Introduce hardware maximum timeout in watchdog core Guenter Roeck
2016-02-28 13:18 ` Wim Van Sebroeck
2016-02-28 18:43 ` Guenter Roeck
2016-01-26 2:53 ` [PATCH v7 2/9] watchdog: Introduce WDOG_HW_RUNNING flag Guenter Roeck
2016-01-26 2:53 ` [PATCH v7 3/9] watchdog: Make set_timeout function optional Guenter Roeck
2016-01-26 2:53 ` [PATCH v7 4/9] watchdog: Add support for minimum time between heartbeats Guenter Roeck
2016-01-26 8:07 ` Uwe Kleine-König
2016-01-26 14:42 ` Guenter Roeck
2016-01-26 2:53 ` [PATCH v7 5/9] watchdog: Simplify update_worker Guenter Roeck
2016-01-26 2:53 ` [RFT PATCH v7 6/9] watchdog: imx2: Convert to use infrastructure triggered keepalives Guenter Roeck
2016-01-29 19:40 ` Guenter Roeck
2016-01-26 2:53 ` [RFT PATCH v7 7/9] watchdog: retu: " Guenter Roeck
2016-01-26 2:53 ` [RFT PATCH v7 8/9] watchdog: at91sam9: " Guenter Roeck
2016-01-26 2:53 ` [RFT PATCH v7 9/9] watchdog: dw_wdt: Convert to use watchdog infrastructure Guenter Roeck
2016-01-29 17:52 ` Doug Anderson
2016-01-29 18:24 ` Guenter Roeck
2016-01-26 8:09 ` Uwe Kleine-König [this message]
2016-01-26 14:43 ` [PATCH v7 0/9] watchdog: Add support for keepalives triggered by infrastructure 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=20160126080904.GV3338@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=corbet@lwn.net \
--cc=dianders@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=patchwork@patchwork.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 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.