From: Rob Herring <robh@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, bhelgaas@google.com, marex@denx.de,
shawnguo@kernel.org, Fabio Estevam <festevam@denx.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 3/5] dt-bindings: soc: Add i.MX6SX General Purpose Register
Date: Wed, 7 Jun 2023 14:31:46 -0600 [thread overview]
Message-ID: <20230607203146.GA3970300-robh@kernel.org> (raw)
In-Reply-To: <CAOMZO5BAoT=Mi_Ac_qD-eu37nJkBMpF5HJ54MbrAtPakw-BZCQ@mail.gmail.com>
On Mon, May 22, 2023 at 06:53:10PM -0300, Fabio Estevam wrote:
> On Mon, May 22, 2023 at 6:32 PM Rob Herring <robh@kernel.org> wrote:
>
> > 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/dt-review-ci/linux/Documentation/devicetree/bindings/soc/imx/fsl,imx6sx-gpr.example.dtb: syscon@20e4000: bridge@18:compatible:0: 'fsl,imx6sx-ldb' is not one of ['fsl,imx8mp-ldb', 'fsl,imx93-ldb']
> > From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/soc/imx/fsl,imx6sx-gpr.yaml
>
> Same comment as in 2/5 applies here too:
>
> Dependency: This depends on bd60d98a11da ("dt-bindings: display:
> bridge: ldb: Adjust imx6sx entries"),
> which is available on linux-next.
No such commit hash nor is
Documentation/bindings/display/bridge/fsl,ldb.yaml a file in next.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-07 20:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 20:14 [PATCH v6 1/5] PCI: imx6: Use a more specific i.MX6SX GPR compatible Fabio Estevam
2023-05-22 20:14 ` [PATCH v6 2/5] dt-bindings: display: bridge: ldb: Adjust imx6sx entries Fabio Estevam
2023-05-22 22:06 ` Conor Dooley
2023-05-23 2:27 ` Marek Vasut
2023-05-22 20:14 ` [PATCH v6 3/5] dt-bindings: soc: Add i.MX6SX General Purpose Register Fabio Estevam
2023-05-22 21:32 ` Rob Herring
2023-05-22 21:53 ` Fabio Estevam
2023-06-07 20:31 ` Rob Herring [this message]
2023-06-07 21:07 ` Fabio Estevam
2023-05-22 22:10 ` Conor Dooley
2023-05-23 2:28 ` Marek Vasut
2023-05-22 20:14 ` [PATCH v6 4/5] ARM: dts: imx6sx: Add LDB support Fabio Estevam
2023-05-23 2:29 ` Marek Vasut
2023-05-23 11:34 ` Fabio Estevam
2023-05-23 12:56 ` Marek Vasut
2023-05-22 20:14 ` [PATCH v6 5/5] soc: imx: imx6sx-gpr: Introduce a GPR driver Fabio Estevam
2023-05-23 2:30 ` Marek Vasut
2023-05-23 11:44 ` Fabio Estevam
2023-05-23 12:57 ` Marek Vasut
2023-05-23 21:13 ` Fabio Estevam
2023-05-23 23:30 ` Marek Vasut
2023-05-23 23:41 ` Fabio Estevam
2023-05-23 2:27 ` [PATCH v6 1/5] PCI: imx6: Use a more specific i.MX6SX GPR compatible Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230607203146.GA3970300-robh@kernel.org \
--to=robh@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marex@denx.de \
--cc=shawnguo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).