From: lukas.funke-oss@weidmueller.com
To: u-boot@lists.denx.de
Cc: E Shattow <lucent@gmail.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Lukas Funke <lukas.funke@weidmueller.com>,
Atish Patra <atishp@atishpatra.org>,
Aurelien Jarno <aurelien@aurel32.net>,
Chanho Park <chanho61.park@samsung.com>,
Green Wan <green.wan@sifive.com>,
Minda Chen <minda.chen@starfivetech.com>,
Nylon Chen <nylon.chen@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Shiji Yang <yangshiji66@outlook.com>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Subject: [PATCH v3 0/2] riscv: Rename spl_soc_init() to spl_dram_init()
Date: Wed, 24 Apr 2024 09:43:37 +0200 [thread overview]
Message-ID: <20240424074339.210851-1-lukas.funke-oss@weidmueller.com> (raw)
From: Lukas Funke <lukas.funke@weidmueller.com>
This patch series renames spl_soc_init() to spl_dram_init() since the
purpose of the function is to initialization the DRAM on sifive/starfive
boards. spl_dram_init() is a commonly used function for this purpose.
Changes in v3:
- Reorganize patches such that each patch can be built individually
Changes in v2:
- capitalized acronym DRAM
Lukas Funke (2):
board: sifive: Rename spl_soc_init() to spl_dram_init()
board: starfive: Rename spl_soc_init() to spl_dram_init()
arch/riscv/cpu/fu540/spl.c | 2 +-
arch/riscv/cpu/fu740/spl.c | 2 +-
arch/riscv/cpu/jh7110/spl.c | 2 +-
arch/riscv/include/asm/arch-fu540/spl.h | 2 +-
arch/riscv/include/asm/arch-fu740/spl.h | 2 +-
arch/riscv/include/asm/arch-jh7110/spl.h | 2 +-
board/sifive/unleashed/spl.c | 4 ++--
board/sifive/unmatched/spl.c | 4 ++--
board/starfive/visionfive2/spl.c | 4 ++--
9 files changed, 12 insertions(+), 12 deletions(-)
--
2.30.2
next reply other threads:[~2024-04-24 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 7:43 lukas.funke-oss [this message]
2024-04-24 7:43 ` [PATCH v3 1/2] board: sifive: Rename spl_soc_init() to spl_dram_init() lukas.funke-oss
2024-04-26 7:51 ` Leo Liang
2024-04-24 7:43 ` [PATCH v3 2/2] board: starfive: " lukas.funke-oss
2024-04-24 11:01 ` Heinrich Schuchardt
2024-05-02 6:06 ` Lukas Funke
2024-05-02 6:33 ` Leo Liang
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=20240424074339.210851-1-lukas.funke-oss@weidmueller.com \
--to=lukas.funke-oss@weidmueller.com \
--cc=atishp@atishpatra.org \
--cc=aurelien@aurel32.net \
--cc=chanho61.park@samsung.com \
--cc=green.wan@sifive.com \
--cc=lucent@gmail.com \
--cc=lukas.funke@weidmueller.com \
--cc=minda.chen@starfivetech.com \
--cc=nylon.chen@sifive.com \
--cc=palmer@dabbelt.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=yangshiji66@outlook.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).