Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Richard Zhu <hongxing.zhu@nxp.com>,
	robh+dt@kernel.org, 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
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel@pengutronix.de,
	linux-imx@nxp.com
Subject: Re: [RESEND v10 1/4] dt-bindings: imx6q-pcie: Restruct i.MX PCIe schema
Date: Mon, 8 May 2023 08:49:39 +0200	[thread overview]
Message-ID: <4853c769-e1ec-f2e7-aaf7-5b67a2cd6b5f@linaro.org> (raw)
In-Reply-To: <1676441915-1394-2-git-send-email-hongxing.zhu@nxp.com>

On 15/02/2023 07:18, Richard Zhu wrote:
> Restruct i.MX PCIe schema, derive the common properties, thus they can
> be shared by both the RC and Endpoint schema.
> 
> Update the description of fsl,imx6q-pcie.yaml, and move the EP mode
> compatible to fsl,imx6q-pcie-ep.yaml.
> 
> Add support for i.MX8M PCIe Endpoint modes, and update the MAINTAINER
> accordingly.
> 
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> ---
>  .../bindings/pci/fsl,imx6q-pcie-common.yaml   | 279 ++++++++++++++++++
>  .../bindings/pci/fsl,imx6q-pcie-ep.yaml       |  85 ++++++
>  .../bindings/pci/fsl,imx6q-pcie.yaml          | 240 +--------------
>  MAINTAINERS                                   |   2 +
>  4 files changed, 372 insertions(+), 234 deletions(-)

This keeps reporting errors since a month, so I would assume author
would fix his patch... Now failures are in Linus' v6.4-rc1.

Best regards,
Krzysztof


  reply	other threads:[~2023-05-08  6:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15  6:18 [PATCH DTS RESEND v10 0/4] Add i.MX PCIe EP mode support Richard Zhu
2023-02-15  6:18 ` [RESEND v10 1/4] dt-bindings: imx6q-pcie: Restruct i.MX PCIe schema Richard Zhu
2023-05-08  6:49   ` Krzysztof Kozlowski [this message]
2023-05-08  7:26     ` Krzysztof Kozlowski
2023-05-08  7:29       ` Hongxing Zhu
2023-02-15  6:18 ` [RESEND v10 2/4] arm64: dts: Add i.MX8MM PCIe EP support Richard Zhu
2023-02-15  6:18 ` [RESEND v10 3/4] arm64: dts: Add i.MX8MQ " Richard Zhu
2023-02-15  6:18 ` [RESEND v10 4/4] arm64: dts: Add i.MX8MP " Richard Zhu
2023-03-14  1:04 ` [PATCH DTS RESEND v10 0/4] Add i.MX PCIe EP mode support Shawn Guo
2023-04-07  7:53 ` (subset) " Lorenzo Pieralisi

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=4853c769-e1ec-f2e7-aaf7-5b67a2cd6b5f@linaro.org \
    --to=krzysztof.kozlowski@linaro.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=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=marcel.ziswiler@toradex.com \
    --cc=marex@denx.de \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@kernel.org \
    --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