On Wed, 17 Jun 2020 07:51:13 -0700, Douglas Anderson wrote: > From: Ravi Kumar Bokka <rbo...@codeaurora.org> > > This switches the bindings over from txt to yaml. > > Signed-off-by: Ravi Kumar Bokka <rbo...@codeaurora.org> > Signed-off-by: Douglas Anderson <diand...@chromium.org> > --- > > Changes in v3: > - Split conversion to yaml into separate patch new in v3. > - Use 'const' for compatible instead of a 1-entry enum. > - Changed filename to match compatible string. > - Add #address-cells and #size-cells to list of properties. > - Fixed up example. > > .../bindings/nvmem/qcom,qfprom.yaml | 45 +++++++++++++++++++ > .../devicetree/bindings/nvmem/qfprom.txt | 35 --------------- > 2 files changed, 45 insertions(+), 35 deletions(-) > create mode 100644 Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml > delete mode 100644 Documentation/devicetree/bindings/nvmem/qfprom.txt >
My bot found errors running 'make dt_binding_check' on your patch: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/nvmem/qcom,qfprom.example.dt.yaml: example-0: efuse@784000:reg:0: [0, 7880704, 0, 2303] is too long See https://patchwork.ozlabs.org/patch/1311254 If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure dt-schema is up to date: pip3 install git+https://github.com/devicetree-org/dt-schema.git@master --upgrade Please check and re-submit.
