From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-spi@vger.kernel.org
Cc: Heiko Schocher <hs@denx.de>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Holger Brunck <holger.brunck@keymile.com>,
Kumar Gala <galak@kernel.crashing.org>,
devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] powerpc/82xx: remove spidev node from mgcoge
Date: Wed, 24 Aug 2022 15:47:36 +0300 [thread overview]
Message-ID: <1c2685e9-1501-8815-2cf0-b545bb91ca5d@linaro.org> (raw)
In-Reply-To: <20220824082130.21934-3-wsa+renesas@sang-engineering.com>
On 24/08/2022 11:21, Wolfram Sang wrote:
> Commit 956b200a846e ("spi: spidev: Warn loudly if instantiated from DT
> as "spidev"") states that there should not be spidev nodes in DTs.
> Remove this non-HW description. There won't be a regression because it
> won't bind since 2015 anyhow.
>
> Fixes: 5d1d67e361ea ("powerpc/82xx: add SPI support for mgcoge")
> Cc: Heiko Schocher <hs@denx.de>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-08-24 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 8:21 [PATCH 0/2] spi: remove "spidev" nodes from DTs Wolfram Sang
2022-08-24 8:21 ` [PATCH 1/2] ARM: dts: stm32: argon: remove spidev node Wolfram Sang
2022-08-24 12:47 ` Krzysztof Kozlowski
2022-09-12 13:16 ` Alexandre TORGUE
2022-08-24 8:21 ` [PATCH 2/2] powerpc/82xx: remove spidev node from mgcoge Wolfram Sang
2022-08-24 12:47 ` Krzysztof Kozlowski [this message]
2022-08-31 13:14 ` [PATCH 0/2] spi: remove "spidev" nodes from DTs Michael Ellerman
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=1c2685e9-1501-8815-2cf0-b545bb91ca5d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=christophe.leroy@csgroup.eu \
--cc=devicetree@vger.kernel.org \
--cc=galak@kernel.crashing.org \
--cc=holger.brunck@keymile.com \
--cc=hs@denx.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.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).