From: Guenter Roeck <linux@roeck-us.net>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
Wim Van Sebroeck <wim@iguana.be>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Grant Likely <grant.likely@linaro.org>
Subject: Re: [PATCH v3] watchdog: GPIO-controlled watchdog
Date: Fri, 06 Dec 2013 23:14:35 -0800 [thread overview]
Message-ID: <52A2CADB.2070700@roeck-us.net> (raw)
In-Reply-To: <20131207105258.b9597225842794cadd15e08f@mail.ru>
On 12/06/2013 10:52 PM, Alexander Shiyan wrote:
> On Sat, 30 Nov 2013 11:54:32 +0400
> Alexander Shiyan <shc_work@mail.ru> wrote:
>
>> This patch adds a watchdog driver for devices controlled through GPIO,
>> (Analog Devices ADM706, Maxim MAX823, National NE555 etc).
>>
>> Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
>> ---
>> .../devicetree/bindings/watchdog/gpio-wdt.txt | 23 ++
>> drivers/watchdog/Kconfig | 8 +
>> drivers/watchdog/Makefile | 1 +
>> drivers/watchdog/gpio_wdt.c | 254 +++++++++++++++++++++
>> 4 files changed, 286 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/watchdog/gpio-wdt.txt
>> create mode 100644 drivers/watchdog/gpio_wdt.c
> ...
>
> Ping.
>
Wim typically only finds the time to look at pending patches a couple of weeks before
the next commit window opens. I'll send him a reminder with all patches I am aware of
in a week or so. I have this one in my list.
Guenter
next prev parent reply other threads:[~2013-12-07 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 7:54 [PATCH v3] watchdog: GPIO-controlled watchdog Alexander Shiyan
2013-12-01 17:58 ` Guenter Roeck
2013-12-01 19:03 ` Alexander Shiyan
2013-12-01 19:14 ` Guenter Roeck
2014-01-06 20:48 ` Wim Van Sebroeck
2013-12-07 6:52 ` Alexander Shiyan
2013-12-07 7:14 ` Guenter Roeck [this message]
2014-01-06 21:10 ` Wim Van Sebroeck
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=52A2CADB.2070700@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-watchdog@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=shc_work@mail.ru \
--cc=swarren@wwwdotorg.org \
--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