[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <166805230789.3436553.2751149076603069326.robh@kernel.org>
Date: Wed, 9 Nov 2022 21:51:50 -0600
From: Rob Herring <robh@...nel.org>
To: Miquel Raynal <miquel.raynal@...tlin.com>
Cc: linux-arm-kernel@...ts.infradead.org,
Christian Eggers <ceggers@...i.de>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
devicetree@...r.kernel.org, Bartosz Golaszewski <brgl@...ev.pl>,
Rob Herring <robh+dt@...nel.org>,
Luka Perkov <luka.perkov@...tura.hr>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
Michael Walle <michael@...le.cc>, linux-kernel@...r.kernel.org,
Robert Marko <robert.marko@...tura.hr>,
Cory Tusar <cory.tusar@...1solutions.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Subject: Re: [PATCH v3 1/6] dt-bindings: nvmem: Fix example
On Fri, 04 Nov 2022 17:38:28 +0100, Miquel Raynal wrote:
> Despite not being listed nor required within the top level nvmem yaml
> file, the "compatible" property is mandatory and is actually enforced by
> all the nvmem provider bindings.
>
> Unfortunately, the lack of compatible in the nvmem.yaml to level
> description file lead to the example not matching anything and thus not
> being checked at all.
>
> Let's pick a compatible almost randomly (one which is already used with
> the qfprom label) to make the example at least valid on a semantic
> point of view and getting it checked.
>
> Signed-off-by: Miquel Raynal <miquel.raynal@...tlin.com>
> ---
> Documentation/devicetree/bindings/nvmem/nvmem.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists