On Fri, 2023-04-28 at 09:52 -0500, Rob Herring wrote: > External email : Please do not click links or open attachments until > you have verified the sender or the content. > > > On Fri, 28 Apr 2023 18:36:17 +0800, Yi-De Wu wrote: > > From: "Yingshiuan Pan" <yingshiuan.pan@xxxxxxxxxxxx> > > > > Add documentation for GenieZone(gzvm) node. This node informs gzvm > > driver to start probing if geniezone hypervisor is available and > > able to do virtual machine operations. > > > > Signed-off-by: Yingshiuan Pan <yingshiuan.pan@xxxxxxxxxxxx> > > Signed-off-by: Yi-De Wu <yi-de.wu@xxxxxxxxxxxx> > > --- > > .../hypervisor/mediatek,geniezone-hyp.yaml | 31 > > +++++++++++++++++++ > > MAINTAINERS | 1 + > > 2 files changed, 32 insertions(+) > > create mode 100644 > > Documentation/devicetree/bindings/hypervisor/mediatek,geniezone- > > hyp.yaml > > > > My bot found errors running 'make DT_CHECKER_FLAGS=-m > dt_binding_check' > on your patch (DT_CHECKER_FLAGS is new in v5.13): > > yamllint warnings/errors: > > dtschema/dtc warnings/errors: > ./Documentation/devicetree/bindings/hypervisor/mediatek,geniezone- > hyp.yaml: $id: relative path/filename doesn't match actual path or > filename > expected: > https://urldefense.com/v3/__http://devicetree.org/schemas/hypervisor/mediatek,geniezone-hyp.yaml*__;Iw!!CTRNKA9wMg0ARbw!joIOXbICM7UGvy3XBEJvfzSKO7s61efB87_NX5cqpUqpu5ot5cuzw50A8-8ledZT9_7ifsB2sKzxSD0$ > > doc reference errors (make refcheckdocs): > > See > https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230428103622.18291-3-yi-de.wu@xxxxxxxxxxxx > > The base for the series is generally the latest rc1. A different > dependency > should be noted in *this* patch. > > If you already ran 'make dt_binding_check' and didn't see the above > error(s), then make sure 'yamllint' is installed and dt-schema is up > to > date: > > pip3 install dtschema --upgrade > > Please check and re-submit after running the above command yourself. > Note > that DT_SCHEMA_FILES can be set to your schema file to speed up > checking > your schema. However, it must be unset to test all examples with your > schema. > Noted, we've run the yaml check and we are going to re-submit the latest version in v3.