linux-kernel - Re: [PATCH v8 3/4] dt-bindings: irqchip: imx mu work as msi controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 06 Sep 2022 16:41:00 -0500
From:   Rob Herring <robh@...nel.org>
To:     Frank Li <Frank.Li@....com>
Cc:     linux-arm-kernel@...ts.infradead.org, robh+dt@...nel.org,
        linux-kernel@...r.kernel.org, kernel@...gutronix.de,
        devicetree@...r.kernel.org, tglx@...utronix.de, festevam@...il.com,
        ntb@...ts.linux.dev, shawnguo@...nel.org,
        krzysztof.kozlowski+dt@...aro.org, maz@...nel.org, kishon@...com,
        peng.fan@....com, imx@...ts.linux.dev, lorenzo.pieralisi@....com,
        kw@...ux.com, lznuaa@...il.com, jdmason@...zu.us,
        linux-imx@....com, linux-pci@...r.kernel.org,
        s.hauer@...gutronix.de, bhelgaas@...gle.com, aisheng.dong@....com
Subject: Re: [PATCH v8 3/4] dt-bindings: irqchip: imx mu work as msi controller

On Tue, 06 Sep 2022 14:40:51 -0500, Frank Li wrote:
> I.MX mu support generate irq by write a register. Provide msi controller
> support so other driver such as PCI EP can use it by standard msi
> interface as doorbell.
> 
> Signed-off-by: Frank Li <Frank.Li@....com>
> ---
>  .../interrupt-controller/fsl,mu-msi.yaml      | 99 +++++++++++++++++++
>  1 file changed, 99 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.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:
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.example.dtb: msi-controller@...70000: reg-names:0: 'processor-a-side' was expected
	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.yaml
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.example.dtb: msi-controller@...70000: reg-names:1: 'processor-b-side' was expected
	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.yaml
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.example.dtb: msi-controller@...70000: power-domain-names:0: 'processor-a-side' was expected
	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.yaml
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.example.dtb: msi-controller@...70000: power-domain-names:1: 'processor-b-side' was expected
	From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.yaml

doc reference errors (make refcheckdocs):

See https://patchwork.ozlabs.org/patch/

This check can fail if there are any dependencies. The base for a patch
series is generally the most recent rc1.

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.