From: "Rob Herring (Arm)" <robh@kernel.org>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: festevam@gmail.com, mani@kernel.org, bhelgaas@google.com,
l.stach@pengutronix.de, kernel@pengutronix.de,
linux-kernel@vger.kernel.org, kwilczynski@kernel.org,
linux-pci@vger.kernel.org, s.hauer@pengutronix.de,
lpieralisi@kernel.org, imx@lists.linux.dev, conor+dt@kernel.org,
krzk+dt@kernel.org, frank.li@nxp.com,
linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v5 2/5] dt-bindings: PCI: imx6q-pcie: Add i.MX94 and i.MX943 PCIe compatible strings
Date: Thu, 12 Mar 2026 05:44:16 -0500 [thread overview]
Message-ID: <177331225647.2535696.15664490600606531279.robh@kernel.org> (raw)
In-Reply-To: <20260312092745.295578-3-hongxing.zhu@nxp.com>
On Thu, 12 Mar 2026 17:27:42 +0800, Richard Zhu wrote:
> Add i.MX94 and i.MX943 PCIe compatible strings and fallback to
> i.MX95 PCIe compatible string.
>
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
> ---
> .../bindings/pci/fsl,imx6q-pcie-ep.yaml | 6 ++++
> .../bindings/pci/fsl,imx6q-pcie.yaml | 28 ++++++++++++-------
> 2 files changed, 24 insertions(+), 10 deletions(-)
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
./Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.yaml:39:13: [warning] wrong indentation: expected 14 but found 12 (indentation)
dtschema/dtc warnings/errors:
doc reference errors (make refcheckdocs):
See https://patchwork.kernel.org/project/devicetree/patch/20260312092745.295578-3-hongxing.zhu@nxp.com
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.
next prev parent reply other threads:[~2026-03-12 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 9:27 [PATCH v5 0/5] Add i.MX943 PCIe supports Richard Zhu
2026-03-12 9:27 ` [PATCH v5 1/5] dt-bindings: PCI: imx6q-pcie: Change maxItems of clocks and clock-names to 6 Richard Zhu
2026-03-12 9:27 ` [PATCH v5 2/5] dt-bindings: PCI: imx6q-pcie: Add i.MX94 and i.MX943 PCIe compatible strings Richard Zhu
2026-03-12 10:44 ` Rob Herring (Arm) [this message]
2026-03-12 13:32 ` Rob Herring
2026-03-13 1:49 ` Hongxing Zhu
2026-03-12 9:27 ` [PATCH v5 3/5] arm64: dts: imx94: add pcie0 and pcie0-ep supports Richard Zhu
2026-03-12 19:13 ` Frank Li
2026-03-12 9:27 ` [PATCH v5 4/5] arm64: dts: imx943: add pcie1 and pcie1-ep supports Richard Zhu
2026-03-12 9:27 ` [PATCH v5 5/5] arm64: dts: imx943-evk: Add pcie[0,1] and pcie-ep[0,1] support Richard Zhu
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=177331225647.2535696.15664490600606531279.robh@kernel.org \
--to=robh@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=s.hauer@pengutronix.de \
/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