From: Leo Liang <ycliang@andestech.com>
To: Lukas Funke <lukas.funke-oss@weidmueller.com>
Cc: <u-boot@lists.denx.de>, E Shattow <lucent@gmail.com>,
Lukas Funke <lukas.funke@weidmueller.com>,
Minda Chen <minda.chen@starfivetech.com>,
Simon Glass <sjg@chromium.org>,
Yanhong Wang <yanhong.wang@starfivetech.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v3 2/2] board: starfive: Rename spl_soc_init() to spl_dram_init()
Date: Thu, 2 May 2024 14:33:13 +0800 [thread overview]
Message-ID: <ZjMzqeOi-xHjfnmG@swlinux02> (raw)
In-Reply-To: <feb52626-c8ac-4ccd-939a-ea0d7495fe3c@weidmueller.com>
On Thu, May 02, 2024 at 08:06:43AM +0200, Lukas Funke wrote:
> [EXTERNAL MAIL]
>
> On 24.04.2024 13:01, Heinrich Schuchardt wrote:
> > On 24.04.24 09:43, lukas.funke-oss@weidmueller.com wrote:
> > > From: Lukas Funke <lukas.funke@weidmueller.com>
> > >
> > > Rename spl_soc_init() to spl_dram_init() because the generic function
> > > name does not reflect what the function actually does. Also
> > > spl_dram_init() is commonly used for dram initialization and should be
> > > called from board_init_f().
> > >
> > > Signed-off-by: Lukas Funke <lukas.funke@weidmueller.com>
> >
> > Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> Any objection on this one?
Hi Lukas,
This patch has been merged to u-boot-riscv. Thanks!
Best regards,
Leo
prev parent reply other threads:[~2024-05-02 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 7:43 [PATCH v3 0/2] riscv: Rename spl_soc_init() to spl_dram_init() lukas.funke-oss
2024-04-24 7:43 ` [PATCH v3 1/2] board: sifive: " 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 [this message]
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=ZjMzqeOi-xHjfnmG@swlinux02 \
--to=ycliang@andestech.com \
--cc=lucent@gmail.com \
--cc=lukas.funke-oss@weidmueller.com \
--cc=lukas.funke@weidmueller.com \
--cc=minda.chen@starfivetech.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=yanhong.wang@starfivetech.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).