From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>, Tero Kristo <t-kristo@ti.com>,
devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: watchdog: ti,rti-wdt: Fix assigned-clock-parents
Date: Tue, 7 Dec 2021 09:23:10 +0100 [thread overview]
Message-ID: <Ya8Z7gReKtZA+BGw@orome.fritz.box> (raw)
In-Reply-To: <20211206174028.2294330-1-robh@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
On Mon, Dec 06, 2021 at 11:40:28AM -0600, Rob Herring wrote:
> With 'unevaluatedProperties' support implemented, the ti,rti-wdt example
> has the following warning:
>
> /home/rob/proj/git/linux-dt/.build-arm64/Documentation/devicetree/bindings/watchdog/ti,rti-wdt.example.dt.yaml: watchdog@2200000: Unevaluated properties are not allowed ('assigned-clock-parents' was unexpected)
>
> The problem is the schema has a typo in 'assigned-clocks-parents'. As
> it is not required to list assigned clocks in bindings, just drop the
> property definitions to fix this.
>
> Cc: Wim Van Sebroeck <wim@linux-watchdog.org>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: Tero Kristo <t-kristo@ti.com>
> Cc: linux-watchdog@vger.kernel.org
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Documentation/devicetree/bindings/watchdog/ti,rti-wdt.yaml | 6 ------
> 1 file changed, 6 deletions(-)
Reviewed-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-12-07 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 17:40 [PATCH] dt-bindings: watchdog: ti,rti-wdt: Fix assigned-clock-parents Rob Herring
2021-12-06 19:47 ` Guenter Roeck
2021-12-07 8:23 ` Thierry Reding [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=Ya8Z7gReKtZA+BGw@orome.fritz.box \
--to=thierry.reding@gmail.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@kernel.org \
--cc=t-kristo@ti.com \
--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).