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@xxxxxxxxxxx> > --- > Documentation/devicetree/bindings/nvmem/nvmem.yaml | 1 + > 1 file changed, 1 insertion(+) > Acked-by: Rob Herring <robh@xxxxxxxxxx>
