From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] arm64: dts: meson: Fix erroneous SPI bus warnings
Date: Fri, 14 Sep 2018 12:39:47 -0700 [thread overview]
Message-ID: <7hk1nnuav0.fsf@baylibre.com> (raw)
In-Reply-To: <20180913181245.25484-17-robh@kernel.org> (Rob Herring's message of "Thu, 13 Sep 2018 13:12:41 -0500")
Rob Herring <robh@kernel.org> writes:
> dtc has new checks for SPI buses. The meson dts files have a node named
> spi' which causes false positive warnings. As the node is a pinctrl child
> node, change the node name to be 'spi-pins' to fix the warnings.
>
> arch/arm64/boot/dts/amlogic/meson-gxbb-nanopi-k2.dtb: Warning (spi_bus_bridge): /soc/periphs at c8834000/pinctrl at 4b0/spi: incorrect #address-cells for SPI bus
>
> Cc: Carlo Caione <carlo@caione.org>
> Cc: Kevin Hilman <khilman@baylibre.com>
> Cc: linux-amlogic at lists.infradead.org
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Please apply to the sub-arch tree. The dtc changes haven't landed, but
> will for 4.20.
Applied, will queue for v4.20.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: meson: Fix erroneous SPI bus warnings
Date: Fri, 14 Sep 2018 12:39:47 -0700 [thread overview]
Message-ID: <7hk1nnuav0.fsf@baylibre.com> (raw)
In-Reply-To: <20180913181245.25484-17-robh@kernel.org> (Rob Herring's message of "Thu, 13 Sep 2018 13:12:41 -0500")
Rob Herring <robh@kernel.org> writes:
> dtc has new checks for SPI buses. The meson dts files have a node named
> spi' which causes false positive warnings. As the node is a pinctrl child
> node, change the node name to be 'spi-pins' to fix the warnings.
>
> arch/arm64/boot/dts/amlogic/meson-gxbb-nanopi-k2.dtb: Warning (spi_bus_bridge): /soc/periphs at c8834000/pinctrl at 4b0/spi: incorrect #address-cells for SPI bus
>
> Cc: Carlo Caione <carlo@caione.org>
> Cc: Kevin Hilman <khilman@baylibre.com>
> Cc: linux-amlogic at lists.infradead.org
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Please apply to the sub-arch tree. The dtc changes haven't landed, but
> will for 4.20.
Applied, will queue for v4.20.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Rob Herring <robh@kernel.org>
Cc: Carlo Caione <carlo@caione.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: meson: Fix erroneous SPI bus warnings
Date: Fri, 14 Sep 2018 12:39:47 -0700 [thread overview]
Message-ID: <7hk1nnuav0.fsf@baylibre.com> (raw)
In-Reply-To: <20180913181245.25484-17-robh@kernel.org> (Rob Herring's message of "Thu, 13 Sep 2018 13:12:41 -0500")
Rob Herring <robh@kernel.org> writes:
> dtc has new checks for SPI buses. The meson dts files have a node named
> spi' which causes false positive warnings. As the node is a pinctrl child
> node, change the node name to be 'spi-pins' to fix the warnings.
>
> arch/arm64/boot/dts/amlogic/meson-gxbb-nanopi-k2.dtb: Warning (spi_bus_bridge): /soc/periphs@c8834000/pinctrl@4b0/spi: incorrect #address-cells for SPI bus
>
> Cc: Carlo Caione <carlo@caione.org>
> Cc: Kevin Hilman <khilman@baylibre.com>
> Cc: linux-amlogic@lists.infradead.org
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> Please apply to the sub-arch tree. The dtc changes haven't landed, but
> will for 4.20.
Applied, will queue for v4.20.
Kevin
next prev parent reply other threads:[~2018-09-14 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 18:12 [PATCH] arm64: dts: meson: Fix erroneous SPI bus warnings Rob Herring
2018-09-13 18:12 ` Rob Herring
2018-09-13 18:12 ` Rob Herring
2018-09-14 19:39 ` Kevin Hilman [this message]
2018-09-14 19:39 ` Kevin Hilman
2018-09-14 19:39 ` Kevin Hilman
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=7hk1nnuav0.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.