From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/5] Update Davinci watchdog driver
Date: Sat, 14 Dec 2013 14:17:40 -0500 [thread overview]
Message-ID: <52ACAED4.7000305@ti.com> (raw)
In-Reply-To: <52A5EF6B.6060700@ti.com>
Wim,
On Monday 09 December 2013 11:27 AM, Santosh Shilimkar wrote:
> Wim,
>
> On Wednesday 04 December 2013 02:39 PM, Ivan Khoronzhuk wrote:
>> These patches are intended to update Davinci watchdog to use WDT core
>> and reuse driver for keystone arch, because Keystone uses the similar
>> IP like Davinci.
>>
>
> [..]
>
>> v4..v5:
>> - watchdog: davinci: change driver to use WDT core
>> switched off CONFIG_WATCHDOG_NOWAYOUT option
>>
> Can you please apply the series to your watchdog tree ?
> Do let me know if you want us to prepare a git branch
> to pull from.
>
ping..
Regards,
Santosh
next prev parent reply other threads:[~2013-12-14 19:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 19:39 [PATCH v5 0/5] Update Davinci watchdog driver Ivan Khoronzhuk
2013-12-04 19:39 ` [PATCH v5 1/5] watchdog: davinci: change driver to use WDT core Ivan Khoronzhuk
2013-12-04 20:48 ` Guenter Roeck
2013-12-05 11:26 ` [PATCH v6 " Ivan Khoronzhuk
2013-12-04 19:39 ` [PATCH v5 2/5] watchdog: davinci: use davinci_wdt_device structure to hold device data Ivan Khoronzhuk
2013-12-04 19:39 ` [PATCH v5 3/5] watchdog: davinci: add GET_TIMELEFT option support Ivan Khoronzhuk
2013-12-04 19:39 ` [PATCH v5 4/5] watchdog: davinci: add "timeout-sec" property Ivan Khoronzhuk
2013-12-04 19:39 ` [PATCH v5 5/5] watchdog: davinci: reuse driver for keystone arch Ivan Khoronzhuk
2013-12-09 16:27 ` [PATCH v5 0/5] Update Davinci watchdog driver Santosh Shilimkar
2013-12-14 19:17 ` Santosh Shilimkar [this message]
2013-12-26 17:55 ` Santosh Shilimkar
[not found] ` <20131226181725.GL10136@spo001.leaseweb.com>
2013-12-26 18:20 ` Santosh Shilimkar
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=52ACAED4.7000305@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 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).