U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 2/3] riscv: cpu: generic: fallback to generic cleanup_before_linux()
Date: Mon, 3 Feb 2025 11:52:31 +0800	[thread overview]
Message-ID: <Z6A9f9_CbXNoucDX@swlinux02> (raw)
In-Reply-To: <20250123091134.63634-4-ziyao@disroot.org>

On Thu, Jan 23, 2025 at 09:11:34AM +0000, Yao Zi wrote:
> The current implementation is equivalent to the fallback one, so
> this shouldn't change any behaviour but cleans the code up only.
> 
> Signed-off-by: Yao Zi <ziyao@disroot.org>
> ---
>  arch/riscv/cpu/generic/Makefile |  1 -
>  arch/riscv/cpu/generic/cpu.c    | 22 ----------------------
>  2 files changed, 23 deletions(-)
>  delete mode 100644 arch/riscv/cpu/generic/cpu.c

Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>

  reply	other threads:[~2025-02-03  3:52 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 [this message]
2025-01-23  9:11 ` [RFC PATCH 3/3] riscv: cpu: jh7110: " Yao Zi
2025-02-03  3:53   ` Leo Liang
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=Z6A9f9_CbXNoucDX@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