summaryrefslogtreecommitdiffstats
path: root/drivers/nvmem/Kconfig
diff options
context:
space:
mode:
authorMiquel Raynal <miquel.raynal@bootlin.com>2022-11-18 06:39:25 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2022-11-23 19:44:52 +0100
commit42b868b032901075f8e9bdcd8d700cb9c0d03ba5 (patch)
treec85361840fdd5d6dc622a663cc2094edabbab2f6 /drivers/nvmem/Kconfig
parent06aac0e11960a7ddccc1888326b5906d017e0f24 (diff)
downloadlinux-stable-42b868b032901075f8e9bdcd8d700cb9c0d03ba5.tar.gz
linux-stable-42b868b032901075f8e9bdcd8d700cb9c0d03ba5.tar.bz2
linux-stable-42b868b032901075f8e9bdcd8d700cb9c0d03ba5.zip
dt-bindings: nvmem: Fix example
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@bootlin.com> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Link: https://lore.kernel.org/r/20221118063932.6418-7-srinivas.kandagatla@linaro.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/nvmem/Kconfig')
0 files changed, 0 insertions, 0 deletions