From: Conor Dooley <conor@kernel.org>
To: linux-riscv@lists.infradead.org, Conor Dooley <conor@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
stable@vger.kernel.org, Valentina.FernandezAlanis@microchip.com,
Cyril.Jean@microchip.com,
Daire McNamara <daire.mcnamara@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Jamie Gibbons <jamie.gibbons@microchip.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] riscv: dts: microchip: remove BeagleV Fire fabric.dtsi
Date: Thu, 23 Oct 2025 19:38:55 +0100 [thread overview]
Message-ID: <20251023-feminism-rewrap-39719eb7832a@spud> (raw)
In-Reply-To: <20251021-dastardly-washbowl-b8c4ec1745db@spud>
From: Conor Dooley <conor.dooley@microchip.com>
On Tue, 21 Oct 2025 16:38:37 +0100, Conor Dooley wrote:
> At the time of adding the fabric.dtsi for the BeagleV Fire, we thought
> that the fabric nodes in the Beagle supplied images were stable. They
> are not, which has lead to nodes present in the devicetree that are not
> in the programmed FPGA images. This is obviously problematic, and these
> nodes must be removed.
>
> --
>
> [...]
Applied to riscv-dt-fixes, thanks!
[1/1] riscv: dts: microchip: remove BeagleV Fire fabric.dtsi
https://git.kernel.org/conor/c/5ef13c363640
Thanks,
Conor.
prev parent reply other threads:[~2025-10-23 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 15:38 [PATCH v1] riscv: dts: microchip: remove BeagleV Fire fabric.dtsi Conor Dooley
2025-10-23 18:38 ` 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=20251023-feminism-rewrap-39719eb7832a@spud \
--to=conor@kernel.org \
--cc=Cyril.Jean@microchip.com \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jamie.gibbons@microchip.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=stable@vger.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