From: Guenter Roeck <linux@roeck-us.net>
To: Doug Anderson <dianders@chromium.org>
Cc: "linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"Wim Van Sebroeck" <wim@iguana.be>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Timo Kokkonen" <timo.kokkonen@offcode.fi>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [PATCH v8 06/10] watchdog: dw_wdt: Convert to use watchdog infrastructure
Date: Wed, 2 Mar 2016 11:39:48 -0800 [thread overview]
Message-ID: <20160302193948.GA3006@roeck-us.net> (raw)
In-Reply-To: <CAD=FV=U=FC7jA5=0nP+=wWOxiiDLsCop0+8=o=+j7FvPa2ZvgA@mail.gmail.com>
On Tue, Mar 01, 2016 at 02:59:06PM -0800, Doug Anderson wrote:
> Guenter,
>
> On Sun, Feb 28, 2016 at 1:12 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> > Convert driver to use watchdog infrastructure. This includes
> > infrastructure support to handle watchdog keepalive if the watchdog
> > is running while the watchdog device is closed.
> >
> > Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> >
> > ---
> > v8: max_hw_timeout_ms -> max_hw_heartbeat_ms
> > Rebased to v4.5-rc5
> > v7: Set max_hw_timeout_ms
> > Rebased to v4.5-rc1
> > v6: Added patch
> > ---
> > drivers/watchdog/Kconfig | 1 +
> > drivers/watchdog/dw_wdt.c | 323 +++++++++++++++++-----------------------------
> > 2 files changed, 117 insertions(+), 207 deletions(-)
>
> I re-ran the same set of tests I ran against v7. They all still pass.
>
> Tested-by: Douglas Anderson <dianders@chromium.org>
Thanks a lot!
Guenter
next prev parent reply other threads:[~2016-03-02 19:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 21:12 [PATCH v8 0/10] watchdog: Add support for keepalives triggered by infrastructure Guenter Roeck
2016-02-28 21:12 ` [PATCH v8 01/10] watchdog: Make set_timeout function optional Guenter Roeck
2016-02-28 21:12 ` [PATCH v8 02/10] watchdog: Introduce hardware maximum heartbeat in watchdog core Guenter Roeck
2016-02-28 21:12 ` [PATCH v8 03/10] watchdog: Introduce WDOG_HW_RUNNING flag Guenter Roeck
2016-02-28 21:12 ` [PATCH v8 04/10] watchdog: Make stop function optional Guenter Roeck
2016-02-28 21:12 ` [PATCH v8 05/10] watchdog: Add support for minimum time between heartbeats Guenter Roeck
2016-02-28 21:12 ` [PATCH v8 06/10] watchdog: dw_wdt: Convert to use watchdog infrastructure Guenter Roeck
2016-03-01 22:59 ` Doug Anderson
2016-03-02 19:39 ` Guenter Roeck [this message]
2016-02-28 21:12 ` [PATCH v8 07/10] watchdog: imx2: Convert to use infrastructure triggered keepalives Guenter Roeck
2016-02-28 21:12 ` [RFC PATCH v8 08/10] watchdog: retu: " Guenter Roeck
2016-02-28 21:12 ` [RFC PATCH v8 09/10] watchdog: at91sam9: " Guenter Roeck
2016-02-28 21:12 ` [RFC PATCH v8 10/10] watchdog: gpio: " Guenter Roeck
2016-03-06 10:49 ` [PATCH v8 0/10] watchdog: Add support for keepalives triggered by infrastructure Wim Van Sebroeck
2016-03-07 17:37 ` Guenter Roeck
2016-03-07 18:50 ` Wim Van Sebroeck
2016-03-08 0:39 ` Guenter Roeck
2016-03-07 3:03 ` 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=20160302193948.GA3006@roeck-us.net \
--to=linux@roeck-us.net \
--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=timo.kokkonen@offcode.fi \
--cc=u.kleine-koenig@pengutronix.de \
--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).