From: Samuel Holland <samuel.holland@sifive.com>
To: Conor Dooley <conor@kernel.org>, linux-riscv@lists.infradead.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Daire McNamara <daire.mcnamara@microchip.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Emil Renner Berthing <kernel@esmil.dk>,
Jisheng Zhang <jszhang@kernel.org>, Guo Ren <guoren@kernel.org>,
Fu Wei <wefu@redhat.com>, Chen Wang <unicorn_wang@outlook.com>,
devicetree@vger.kernel.org, linux-sunxi@lists.linux.dev,
linux-renesas-soc@vger.kernel.org
Subject: Re: [RFC v2 2/6] riscv: dts: sifive: convert isa detection to new properties
Date: Mon, 25 Sep 2023 12:38:58 -0500 [thread overview]
Message-ID: <a43ef21e-ce26-45ee-be28-526238e3e88f@sifive.com> (raw)
In-Reply-To: <20230922081351.30239-4-conor@kernel.org>
On 2023-09-22 3:13 AM, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Convert the fu540 and fu740 devicetrees to use the new properties
> "riscv,isa-base" & "riscv,isa-extensions".
> For compatibility with other projects, "riscv,isa" remains.
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 15 +++++++++++++++
> arch/riscv/boot/dts/sifive/fu740-c000.dtsi | 15 +++++++++++++++
> 2 files changed, 30 insertions(+)
Reviewed-by: Samuel Holland <samuel.holland@sifive.com>
next prev parent reply other threads:[~2023-09-25 17:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 8:13 [RFC v2 0/6] riscv,isa-extensions additions Conor Dooley
2023-09-22 8:13 ` [RFC v2 1/6] riscv: dts: microchip: convert isa detection to new properties Conor Dooley
2023-09-22 8:13 ` [RFC v2 2/6] riscv: dts: sifive: " Conor Dooley
2023-09-25 17:38 ` Samuel Holland [this message]
2023-09-22 8:13 ` [RFC v2 3/6] riscv: dts: starfive: " Conor Dooley
2023-09-22 8:13 ` [RFC v2 4/6] riscv: dts: renesas: " Conor Dooley
2023-09-22 8:13 ` [RFC v2 5/6] riscv: dts: allwinner: " Conor Dooley
2023-09-24 19:42 ` Jernej Škrabec
2023-09-22 8:13 ` [RFC v2 6/6] riscv: dts: thead: " Conor Dooley
2023-09-23 7:50 ` Guo Ren
2023-09-23 10:25 ` Conor Dooley
2023-10-09 1:01 ` Guo Ren
2023-09-23 23:22 ` Icenowy Zheng
2023-09-25 15:59 ` Conor Dooley
2023-09-26 3:15 ` Icenowy Zheng
2023-09-26 9:14 ` Conor Dooley
2023-10-04 12:13 ` Jisheng Zhang
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=a43ef21e-ce26-45ee-be28-526238e3e88f@sifive.com \
--to=samuel.holland@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=guoren@kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=jszhang@kernel.org \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=magnus.damm@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=unicorn_wang@outlook.com \
--cc=wefu@redhat.com \
--cc=wens@csie.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