From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Inochi Amaoto <inochiama@gmail.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
sophgo@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 3/3] riscv: dts: sophgo: switch precise compatible for existed clock device for CV18XX
Date: Sun, 04 May 2025 12:55:41 +0200 [thread overview]
Message-ID: <284f4158408d4047a52d427c9189910064b24d97.camel@gmail.com> (raw)
In-Reply-To: <20250504104553.1447819-4-inochiama@gmail.com>
On Sun, 2025-05-04 at 18:45 +0800, Inochi Amaoto wrote:
> replace newly added precise compatible with old one for existed
> clock device of CV18XX series SoCs.
>
> Signed-off-by: Inochi Amaoto <inochiama@gmail.com>
Reviewed-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
> ---
> arch/riscv/boot/dts/sophgo/cv1800b.dtsi | 2 +-
> arch/riscv/boot/dts/sophgo/cv1812h.dtsi | 2 +-
> arch/riscv/boot/dts/sophgo/sg2002.dtsi | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
--
Alexander Sverdlin.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-05-04 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-04 10:45 [PATCH v2 0/3] riscv: sophgo: cv18xx: dts rework, part 2 Inochi Amaoto
2025-05-04 10:45 ` [PATCH v2 1/3] dt-bindings: clock: sophgo: Use precise compatible for CV1800 series SoC Inochi Amaoto
2025-05-06 16:20 ` Conor Dooley
2025-05-04 10:45 ` [PATCH v2 2/3] clk: sophgo: Add support for newly added precise compatible Inochi Amaoto
2025-05-04 10:55 ` Alexander Sverdlin
2025-05-04 10:45 ` [PATCH v2 3/3] riscv: dts: sophgo: switch precise compatible for existed clock device for CV18XX Inochi Amaoto
2025-05-04 10:55 ` Alexander Sverdlin [this message]
2025-05-06 23:45 ` (subset) [PATCH v2 0/3] riscv: sophgo: cv18xx: dts rework, part 2 Inochi Amaoto
2025-05-13 4:18 ` Inochi Amaoto
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=284f4158408d4047a52d427c9189910064b24d97.camel@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=sophgo@lists.linux.dev \
/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