From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Jeremy Gebben <jgebben@sweptlaser.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-rtc@vger.kernel.org, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] rtc: abx80x: add basic watchdog support
Date: Wed, 12 Sep 2018 13:18:52 +0200 [thread overview]
Message-ID: <20180912111852.GD2760@piout.net> (raw)
In-Reply-To: <20180911172826.7195-1-jgebben@sweptlaser.com>
On 11/09/2018 11:28:24-0600, Jeremy Gebben wrote:
> This patch series adds watchdog support for abracon RTC chips which
> include basic watchdog functionality.
>
> Thank you for reviewing.
>
> Changes in v3 (all in patch 2):
> * fix CONFIG_WATCHDOG dependency again (hopefully correctly this time)
> * don't start hardware when set_timeout is called
> * remove unneeded WDOG_HW_RUNNING bit changes
> * fix abx80x_setup_watchdog()
> * fix formatting of multiline splits
>
> Changes in v2:
> * split out priv structure into a separate patch
> * remove new Kconfig option
> * fix CONFIG_WATCHDOG dependency
> * fix WDT interrupt message
>
>
> Jeremy Gebben (2):
> rtc: abx80x: use a 'priv' struct for client data
> rtc: abx80x: add basic watchdog support
>
> drivers/rtc/Kconfig | 1 +
> drivers/rtc/rtc-abx80x.c | 143 +++++++++++++++++++++++++++++++++++----
> 2 files changed, 132 insertions(+), 12 deletions(-)
>
Applied, thanks.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-09-12 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 17:28 [PATCH v3 0/2] rtc: abx80x: add basic watchdog support Jeremy Gebben
2018-09-11 17:28 ` [PATCH 1/2] rtc: abx80x: use a 'priv' struct for client data Jeremy Gebben
2018-09-11 17:28 ` [PATCH 2/2] rtc: abx80x: add basic watchdog support Jeremy Gebben
2018-09-11 21:49 ` Guenter Roeck
2018-09-12 11:18 ` Alexandre Belloni [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=20180912111852.GD2760@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=jgebben@sweptlaser.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@linux-watchdog.org \
/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.