From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 05/15] ARM: dts: imx: fix PCI bus dtc warnings
Date: Fri, 24 Mar 2017 09:28:36 +0800 [thread overview]
Message-ID: <20170324012831.GB30608@dragon> (raw)
In-Reply-To: <CAL_JsqKmbLP07zKN1SJAoe0xHjzjn80HQDRvqASXvhnUOBgAyA@mail.gmail.com>
+Tim who is the owner of Gateworks Ventana boards.
On Wed, Mar 22, 2017 at 08:53:34AM -0500, Rob Herring wrote:
> On Wed, Mar 22, 2017 at 3:19 AM, Shawn Guo <shawnguo@kernel.org> wrote:
> > On Tue, Mar 21, 2017 at 09:03:03PM -0500, Rob Herring wrote:
> >> dtc recently added PCI bus checks. Fix these warnings.
> >>
> >> Signed-off-by: Rob Herring <robh@kernel.org>
> >> Cc: Shawn Guo <shawnguo@kernel.org>
> >> Cc: Sascha Hauer <kernel@pengutronix.de>
> >> Cc: Fabio Estevam <fabio.estevam@nxp.com>
> >
> > Applied with a couple of changes below.
>
> Thanks. BTW, forget to mention there's still one i.MX warning I did
> not fix. It's with the "sky2 at 8" PCI device node. The unit address is
> completely wrong. The comment says bus #8 which doesn't seem right
> either. The unit address should be "<device num>[,<function]". There
> should be a reg property which also has the bus number.
@Tim, these DTC warnings come from Ventana boards. Can you take care of
them?
Shawn
next prev parent reply other threads:[~2017-03-24 1:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 2:02 [PATCH 01/15] ARM: dts: alpine: fix PCIe node name Rob Herring
2017-03-22 2:03 ` [PATCH 02/15] ARM: dts: marvell: fix PCI bus dtc warnings Rob Herring
2017-03-24 14:17 ` Gregory CLEMENT
2017-03-22 2:03 ` [PATCH 03/15] ARM: dts: ti: " Rob Herring
2017-03-22 2:03 ` [PATCH 04/15] ARM: dts: exynos: " Rob Herring
2017-03-23 19:37 ` Krzysztof Kozlowski
2017-03-22 2:03 ` [PATCH 05/15] ARM: dts: imx: " Rob Herring
2017-03-22 8:19 ` Shawn Guo
2017-03-22 13:53 ` Rob Herring
2017-03-24 1:28 ` Shawn Guo [this message]
2017-03-22 2:03 ` [PATCH 06/15] ARM: dts: r8a779x: " Rob Herring
2017-03-22 8:58 ` Geert Uytterhoeven
2017-03-22 13:47 ` Rob Herring
2017-03-22 14:06 ` Geert Uytterhoeven
2017-03-24 7:06 ` Simon Horman
2017-03-24 7:59 ` Geert Uytterhoeven
2017-03-22 2:03 ` [PATCH 07/15] ARM: dts: spear13xx: " Rob Herring
2017-03-22 4:11 ` Viresh Kumar
2017-03-22 2:03 ` [PATCH 08/15] ARM: dts: tegra: " Rob Herring
2017-06-13 14:51 ` Thierry Reding
2017-03-22 2:03 ` [PATCH 09/15] ARM: dts: versatile: " Rob Herring
2017-03-22 2:03 ` [PATCH 10/15] ARM: dts: bcm: fix msi-controller name and unit address Rob Herring
2017-03-22 6:07 ` Ray Jui
2017-03-22 17:16 ` Florian Fainelli
2017-03-22 2:03 ` [PATCH 11/15] arm64: dts: nvidia: fix PCI bus dtc warnings Rob Herring
2017-06-13 14:52 ` Thierry Reding
2017-03-22 2:03 ` [PATCH 12/15] arm64: dts: apm: " Rob Herring
2017-03-22 2:03 ` [PATCH 13/15] arm64: dts: juno: " Rob Herring
2017-03-22 11:56 ` Liviu Dudau
2017-03-22 2:03 ` [PATCH 14/15] arm64: dts: broadcom: " Rob Herring
2017-03-22 5:36 ` Jayachandran C.
2017-03-22 2:03 ` [PATCH 15/15] arm64: dts: xilinx: " Rob Herring
2017-03-23 14:35 ` Michal Simek
2017-03-22 8:01 ` [PATCH 01/15] ARM: dts: alpine: fix PCIe node name Antoine Tenart
2017-03-24 17:00 ` Arnd Bergmann
2017-03-24 18:25 ` Antoine Tenart
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=20170324012831.GB30608@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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