From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Rob Herring <robh@kernel.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Andrew Lunn" <andrew@lunn.ch>,
linux-pwm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: gpio: mvebu: Fix "unevaluatedProperties" to be false
Date: Mon, 5 Feb 2024 09:29:51 +0100 [thread overview]
Message-ID: <CAMRc=Mf0ohQ4Cav2wSDOHydhrSDm8fiL+cjv4hR0m7=8UBDkUw@mail.gmail.com> (raw)
In-Reply-To: <20240202222352.1652745-1-robh@kernel.org>
On Fri, Feb 2, 2024 at 11:24 PM Rob Herring <robh@kernel.org> wrote:
>
> Schemas need "unevaluatedProperties" or "additionalProperties" to be
> false in order to disallow undefined properties. Only common or
> otherwise incomplete schemas should allow undefined properties.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Documentation/devicetree/bindings/gpio/gpio-mvebu.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/gpio/gpio-mvebu.yaml b/Documentation/devicetree/bindings/gpio/gpio-mvebu.yaml
> index f1bd1e6b2e1f..33d4e4716516 100644
> --- a/Documentation/devicetree/bindings/gpio/gpio-mvebu.yaml
> +++ b/Documentation/devicetree/bindings/gpio/gpio-mvebu.yaml
> @@ -115,7 +115,7 @@ allOf:
> required:
> - reg
>
> -unevaluatedProperties: true
> +unevaluatedProperties: false
>
> examples:
> - |
> --
> 2.43.0
>
Applied, thanks!
Bart
prev parent reply other threads:[~2024-02-05 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 22:23 [PATCH] dt-bindings: gpio: mvebu: Fix "unevaluatedProperties" to be false Rob Herring
2024-02-05 8:29 ` Bartosz Golaszewski [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='CAMRc=Mf0ohQ4Cav2wSDOHydhrSDm8fiL+cjv4hR0m7=8UBDkUw@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=u.kleine-koenig@pengutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).