From: Rob Herring <robh@kernel.org>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: krzysztof.kozlowski+dt@linaro.org, l.stach@pengutronix.de,
shawnguo@kernel.org, lorenzo.pieralisi@arm.com, peng.fan@nxp.com,
marex@denx.de, marcel.ziswiler@toradex.com,
tharvey@gateworks.com, frank.li@nxp.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
linux-imx@nxp.com
Subject: Re: [PATCH v7 1/5] dt-bindings: imx6q-pcie: Prepare to separate the Endpoint binding document
Date: Mon, 30 Jan 2023 16:31:08 -0600 [thread overview]
Message-ID: <20230130223108.GA3642291-robh@kernel.org> (raw)
In-Reply-To: <1675049539-14976-2-git-send-email-hongxing.zhu@nxp.com>
On Mon, Jan 30, 2023 at 11:32:15AM +0800, Richard Zhu wrote:
> Prepare to create one separate DT-schema for i.MX PCIe Endpoint
> controllers in another commit.
This and patch 2 should be 1 commit. It is 1 logical change. With only
this commit, fsl,imx8m*-pcie-ep becomes undocumented.
Rob
next prev parent reply other threads:[~2023-01-30 22:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 3:32 [PATCH DTS v7 0/5] Add i.MX PCIe EP mode support Richard Zhu
2023-01-30 3:32 ` [PATCH v7 1/5] dt-bindings: imx6q-pcie: Prepare to separate the Endpoint binding document Richard Zhu
2023-01-30 22:31 ` Rob Herring [this message]
2023-01-31 7:53 ` Hongxing Zhu
2023-01-30 3:32 ` [PATCH v7 2/5] dt-bindings: imx6q-pcie: Add schema for i.MX8M PCIe Endpoint modes Richard Zhu
2023-01-30 22:29 ` Rob Herring
2023-01-31 7:53 ` Hongxing Zhu
2023-01-30 3:32 ` [PATCH v7 3/5] arm64: dts: Add i.MX8MM PCIe EP support Richard Zhu
2023-01-30 3:32 ` [PATCH v7 4/5] arm64: dts: Add i.MX8MQ " Richard Zhu
2023-01-30 3:32 ` [PATCH v7 5/5] arm64: dts: Add i.MX8MP " 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=20230130223108.GA3642291-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank.li@nxp.com \
--cc=hongxing.zhu@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marcel.ziswiler@toradex.com \
--cc=marex@denx.de \
--cc=peng.fan@nxp.com \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.com \
/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).