# Re: \[PATCH 0/4\] dt-bindings: additional/unevaluatedProperties clean-ups

- From: Srinivas Kandagatla \<hidden\>
- Date: 2020-10-06 08:25:18 
- List: linux-input
- Page: https://ratatoskr.run/linux-input/2020/10/6131777
- Thread: https://ratatoskr.run/linux-devicetree/2020/10/6131337/t.md

```text


On 05/10/2020 19:38, Rob Herring wrote:
> The default behavior for json-schema is any unknown property is allowed.
> T
>
> hat is generally not the behavior we want for DT. In order to disallow
> extra properties, schemas need to define 'additionalProperties: false'
> typically. Ideally, we'd just add that automatically with the tools, but
> there are some exceptions so only making things explicit everywhere
> really works. Missing 'additionalProperties' or 'unevaluatedProperties'
> has been a constant source of review comments, so a meta-schema check is
> really needed here.
>
>   Documentation/devicetree/bindings/nvmem/nvmem.yaml     |  2 ++
>   .../devicetree/bindings/nvmem/qcom,qfprom.yaml         |  2 ++

for nvmem parts,

Acked-by: Srinivas Kandagatla <redacted>


thanks,
--srini
```