linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Zhiqiang Hou <Zhiqiang.Hou@nxp.com>, robh+dt@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	devicetree@vger.kernel.org, leoyang.li@nxp.com,
	shawnguo@kernel.org, mark.rutland@arm.com, bhelgaas@google.com,
	Mingkai.Hu@nxp.com, Minghuan.Lian@nxp.com
Subject: Re: [PATCH 0/4] dts/layerscape-pci: removed unsuitable compatible string
Date: Tue, 20 Nov 2018 12:53:14 +0000	[thread overview]
Message-ID: <20181120125314.GA23472@e107981-ln.cambridge.arm.com> (raw)
In-Reply-To: <20181008031428.25293-1-Zhiqiang.Hou@nxp.com>

On Mon, Oct 08, 2018 at 11:14:24AM +0800, Zhiqiang Hou wrote:
> From: Hou Zhiqiang <Zhiqiang.Hou@nxp.com>
> 
> Removed the compatible string "snps,dw-pcie" from FSL layerscape-pci compatible
> string list.
> 
> Hou Zhiqiang (4):
>   doc/layerscape-pci: update the PCIe compatible strings
>   doc/layerscape-pci: removed unsuitable compatible string
>   dts/arm/ls1021a: Clean PCIe controller compatible strings
>   dts/arm64/layerscape: Clean PCIe controller compatible strings
> 
>  .../devicetree/bindings/pci/layerscape-pci.txt       |  7 ++++---
>  arch/arm/boot/dts/ls1021a.dtsi                       |  4 ++--
>  arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi       |  2 +-
>  arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi       |  6 +++---
>  arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi       |  6 +++---
>  arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi       |  6 +++---
>  arch/arm64/boot/dts/freescale/fsl-ls2088a.dtsi       |  8 ++++----
>  arch/arm64/boot/dts/freescale/fsl-ls208xa.dtsi       | 12 ++++--------
>  8 files changed, 24 insertions(+), 27 deletions(-)

Hi Rob,

I assume the dts changes in this series are OK so I am going to
pull them in the PCI tree, please let me know if you see any
problem with that.

Thanks,
Lorenzo

  parent reply	other threads:[~2018-11-20 12:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08  3:14 [PATCH 0/4] dts/layerscape-pci: removed unsuitable compatible string Zhiqiang Hou
2018-10-08  3:14 ` [PATCH 1/4] doc/layerscape-pci: update the PCIe compatible strings Zhiqiang Hou
2018-10-17 13:51   ` Rob Herring
2018-10-25  9:27     ` Z.q. Hou
2018-10-08  3:14 ` [PATCH 2/4] doc/layerscape-pci: removed unsuitable compatible string Zhiqiang Hou
2018-10-17 13:53   ` Rob Herring
2018-10-25  9:28     ` Z.q. Hou
2018-11-22 11:28   ` Lorenzo Pieralisi
2018-11-23  6:22     ` Z.q. Hou
2018-10-08  3:14 ` [PATCH 3/4] dts/arm/ls1021a: Clean PCIe controller compatible strings Zhiqiang Hou
2018-10-08  3:14 ` [PATCH 4/4] dts/arm64/layerscape: " Zhiqiang Hou
2018-11-20 12:53 ` Lorenzo Pieralisi [this message]
2018-11-23  7:36   ` [PATCH 0/4] dts/layerscape-pci: removed unsuitable compatible string Shawn Guo

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=20181120125314.GA23472@e107981-ln.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=Minghuan.Lian@nxp.com \
    --cc=Mingkai.Hu@nxp.com \
    --cc=Zhiqiang.Hou@nxp.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --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).