From: Wolfram Sang <wsa@the-dreams.de>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC v4 1/4] watchdog: renesas-rwdt: add driver
Date: Fri, 18 Mar 2016 08:27:21 +0000 [thread overview]
Message-ID: <20160318082721.GC1388@katana> (raw)
In-Reply-To: <1452287553-18895-2-git-send-email-wsa@the-dreams.de>
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
> How about "renesas,rcar-gen2-rwdt" and "renesas,rcar-gen3-rwdt".
Yes, did this now in V5. And it became useful right away. Because Gen3
cannot have a reset_handler, but Gen2 could if we get ever to support
it.
> > For new bindings, we follow practices set by the rest of the DT crowd.
>
> +1
Understood. I'll try hard to remember this scheme now as the "final and
ultimate solution" :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-18 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 21:12 [RFC v4 1/4] watchdog: renesas-rwdt: add driver Wolfram Sang
2016-01-14 17:30 ` Geert Uytterhoeven
2016-03-17 9:34 ` Wolfram Sang
2016-03-17 9:48 ` Geert Uytterhoeven
2016-03-17 10:09 ` Wolfram Sang
2016-03-18 0:18 ` Simon Horman
2016-03-18 8:27 ` Wolfram Sang [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=20160318082721.GC1388@katana \
--to=wsa@the-dreams.de \
--cc=linux-sh@vger.kernel.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).