From: Rob Herring <robh@kernel.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org, Viresh Kumar <vireshk@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2] dt-bindings: watchdog: sp-805: Convert to Json-schema
Date: Tue, 15 Sep 2020 11:31:55 -0600 [thread overview]
Message-ID: <20200915173155.GA2173707@bogus> (raw)
In-Reply-To: <20200909105046.160991-1-andre.przywara@arm.com>
On Wed, 09 Sep 2020 11:50:46 +0100, Andre Przywara wrote:
> Convert the ARM SP-805 watchdog IP DT binding over to Json-schema.
>
> A straight-forward conversion, but the requirement for providing two
> clocks got strengthened from "should" to "must".
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
> Hi,
>
> this is just the bindings conversion patch, updated to address Rob's
> comments:
> - Remove redundant primecell.yaml inclusion
> - Reference watchdog.yaml
> - Drop now redundant timeout-sec property
> - Add unevaluatedProperties
>
> The DT fixes are independent and now partly already queued, so I am
> posting this separately.
>
> Cheers,
> Andre
>
> .../bindings/watchdog/arm,sp805.txt | 32 ---------
> .../bindings/watchdog/arm,sp805.yaml | 71 +++++++++++++++++++
> 2 files changed, 71 insertions(+), 32 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/watchdog/arm,sp805.txt
> create mode 100644 Documentation/devicetree/bindings/watchdog/arm,sp805.yaml
>
Applied, thanks!
prev parent reply other threads:[~2020-09-15 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 10:50 [PATCH v2] dt-bindings: watchdog: sp-805: Convert to Json-schema Andre Przywara
2020-09-09 11:08 ` Viresh Kumar
2020-09-15 17:31 ` Rob Herring [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=20200915173155.GA2173707@bogus \
--to=robh@kernel.org \
--cc=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=vireshk@kernel.org \
--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 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).