From: Frank Li <Frank.Li@nxp.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
bhelgaas@google.com, frank.li@nxp.com, l.stach@pengutronix.de,
lpieralisi@kernel.org, kwilczynski@kernel.org, mani@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com
Cc: linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org, Richard Zhu <hongxing.zhu@nxp.com>
Subject: Re: [PATCH v3 2/4] arm64: dts: imx94: add pcie0 and pcie0-ep supports
Date: Mon, 9 Mar 2026 15:54:05 -0400 [thread overview]
Message-ID: <20260309195406.1787254-1-Frank.Li@nxp.com> (raw)
In-Reply-To: <20260309084431.3015463-3-hongxing.zhu@nxp.com>
From: Frank Li (AI-BOT) <frank.li@nxp.com>
> + assigned-clocks =<&scmi_clk IMX94_CLK_HSIOPLL_VCO>,
AI: Missing space after '='. Should be "assigned-clocks = <&scmi_clk".
> + reg-names = "dbi","atu", "dbi2", "app", "dma", "addr_space";
AI: Missing space after comma in "dbi","atu". Should be "dbi", "atu".
> + assigned-clocks =<&scmi_clk IMX94_CLK_HSIOPLL_VCO>,
AI: Missing space after '=' again.
Frank
next prev parent reply other threads:[~2026-03-09 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 8:44 [PATCH v3 0/4] Add i.MX943 PCIe supports Richard Zhu
2026-03-09 8:44 ` [PATCH v3 1/4] dt-bindings: PCI: pci-imx6: Fix build warning after adding extref clock Richard Zhu
2026-03-09 15:18 ` Frank Li
2026-03-10 7:59 ` Krzysztof Kozlowski
2026-03-10 8:30 ` Hongxing Zhu
2026-03-09 8:44 ` [PATCH v3 2/4] arm64: dts: imx94: add pcie0 and pcie0-ep supports Richard Zhu
2026-03-09 19:54 ` Frank Li [this message]
2026-03-09 8:44 ` [PATCH v3 3/4] arm64: dts: imx943: add pcie1 and pcie1-ep supports Richard Zhu
2026-03-09 8:44 ` [PATCH v3 4/4] 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=20260309195406.1787254-1-Frank.Li@nxp.com \
--to=frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.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=robh@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