From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.org,
Conor Dooley <conor.dooley@microchip.com>
Cc: conor@kernel.org, Emil Renner Berthing <kernel@esmil.dk>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
William Qiu <william.qiu@starfivetech.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] riscv: dts: starfive: remove non-existant spi device from jh7110-common.dtsi
Date: Wed, 7 Aug 2024 18:26:40 +0100 [thread overview]
Message-ID: <20240807-recital-elixir-f5951f6760d7@spud> (raw)
In-Reply-To: <20240716-majesty-antler-d9bedc7fd0af@wendy>
From: Conor Dooley <conor.dooley@microchip.com>
On Tue, 16 Jul 2024 11:54:00 +0100, Conor Dooley wrote:
> There is no rohm,dh2228fv on any of supported JH7110 boards - in fact
> the dh2228fv almost certainly does not exist as it is not a valid Rohm
> part number. Likely a typo by Maxime when adding the device originally,
> and should have been bh2228fv, but these boards do not have a bh2228fv
> either! Remove it from jh7110-common.dtsi - pretending to have a device
> so that the spidev driver will be bound by Linux is not acceptable.
>
> [...]
Applied to riscv-dt-fixes, thanks!
[1/1] riscv: dts: starfive: remove non-existant spi device from jh7110-common.dtsi
https://git.kernel.org/conor/c/db6efa5e81a5
Thanks,
Conor.
prev parent reply other threads:[~2024-08-07 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 10:54 [PATCH v1] riscv: dts: starfive: remove non-existant spi device from jh7110-common.dtsi Conor Dooley
2024-07-17 8:42 ` Krzysztof Kozlowski
2024-07-26 12:29 ` Emil Renner Berthing
2024-07-26 12:46 ` Conor Dooley
2024-07-26 12:59 ` Emil Renner Berthing
2024-08-07 17:26 ` Conor Dooley [this message]
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=20240807-recital-elixir-f5951f6760d7@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=william.qiu@starfivetech.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