From: Guenter Roeck <linux@roeck-us.net>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Keiji Hayashibara <hayashibara.keiji@socionext.com>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: watchdog: uniphier: Use unevaluatedProperties
Date: Sun, 24 Apr 2022 10:22:13 -0700 [thread overview]
Message-ID: <4c8673de-2503-7f9d-01ae-8f059e8a58ed@roeck-us.net> (raw)
In-Reply-To: <1649317606-21267-1-git-send-email-hayashi.kunihiko@socionext.com>
On 4/7/22 00:46, Kunihiko Hayashi wrote:
> This refers common bindings, so this is preferred for
> unevaluatedProperties instead of additionalProperties.
>
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> .../devicetree/bindings/watchdog/socionext,uniphier-wdt.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/watchdog/socionext,uniphier-wdt.yaml b/Documentation/devicetree/bindings/watchdog/socionext,uniphier-wdt.yaml
> index a059d16cb4f2..90698cfa8f94 100644
> --- a/Documentation/devicetree/bindings/watchdog/socionext,uniphier-wdt.yaml
> +++ b/Documentation/devicetree/bindings/watchdog/socionext,uniphier-wdt.yaml
> @@ -19,7 +19,7 @@ properties:
> required:
> - compatible
>
> -additionalProperties: false
> +unevaluatedProperties: false
>
> examples:
> - |
prev parent reply other threads:[~2022-04-24 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 7:46 [PATCH] dt-bindings: watchdog: uniphier: Use unevaluatedProperties Kunihiko Hayashi
2022-04-13 19:07 ` Rob Herring
2022-04-24 17:22 ` Guenter Roeck [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=4c8673de-2503-7f9d-01ae-8f059e8a58ed@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=hayashibara.keiji@socionext.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=robh+dt@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).