From: Leo Liang <ycliang@andestech.com>
To: Yao Zi <ziyao@disroot.org>
Cc: Rick Chen <rick@andestech.com>, Tom Rini <trini@konsulko.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
Mayuresh Chitale <mchitale@ventanamicro.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
"Simon Glass" <sjg@chromium.org>, <u-boot@lists.denx.de>
Subject: Re: [RFC PATCH 3/3] riscv: cpu: jh7110: fallback to generic cleanup_before_linux()
Date: Mon, 3 Feb 2025 11:53:43 +0800 [thread overview]
Message-ID: <Z6A9x10_Q9vi0Vf1@swlinux02> (raw)
In-Reply-To: <20250123091134.63634-5-ziyao@disroot.org>
On Thu, Jan 23, 2025 at 09:11:35AM +0000, Yao Zi wrote:
> JH7110 SoC requires no specific handling before entering Linux kernel.
> Let's drop the specific implementation to avoid duplication.
>
> Signed-off-by: Yao Zi <ziyao@disroot.org>
> ---
> arch/riscv/cpu/jh7110/Makefile | 1 -
> arch/riscv/cpu/jh7110/cpu.c | 23 -----------------------
> 2 files changed, 24 deletions(-)
> delete mode 100644 arch/riscv/cpu/jh7110/cpu.c
Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
next prev parent reply other threads:[~2025-02-03 3:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 9:11 [RFC PATCH 0/3] Unify implementation of cleanup_before_linux() for RISC-V ports Yao Zi
2025-01-23 9:11 ` [RFC PATCH 1/3] riscv: add a generic implementation for cleanup_before_linux() Yao Zi
2025-02-03 3:51 ` Leo Liang
2025-01-23 9:11 ` [RFC PATCH 2/3] riscv: cpu: generic: fallback to generic cleanup_before_linux() Yao Zi
2025-02-03 3:52 ` Leo Liang
2025-01-23 9:11 ` [RFC PATCH 3/3] riscv: cpu: jh7110: " Yao Zi
2025-02-03 3:53 ` Leo Liang [this message]
2025-01-29 11:28 ` [RFC PATCH 0/3] Unify implementation of cleanup_before_linux() for RISC-V ports Yixun Lan
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=Z6A9x10_Q9vi0Vf1@swlinux02 \
--to=ycliang@andestech.com \
--cc=conor.dooley@microchip.com \
--cc=mchitale@ventanamicro.com \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=ziyao@disroot.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