From: Tom Rini <trini@konsulko.com>
To: Shengyu Qu <wiagn233@outlook.com>
Cc: rick@andestech.com, ycliang@andestech.com,
yanhong.wang@starfivetech.com, sjg@chromium.org,
andre.przywara@arm.com, xypron.glpk@gmx.de, michal.simek@amd.com,
marek.vasut+renesas@mailbox.org, jbx6244@gmail.com,
bmeng@tinylab.org, ganboing@gmail.com,
minda.chen@starfivetech.com, seanga2@gmail.com,
u-boot@lists.denx.de
Subject: Re: [PATCH v6 1/4] Kconfig: Add SPL_SYS_MALLOC_CLEAR_ON_INIT
Date: Thu, 24 Aug 2023 12:31:23 -0400 [thread overview]
Message-ID: <20230824163123.GC3953269@bill-the-cat> (raw)
In-Reply-To: <TY3P286MB26116769A6FC3BB12FB91A77981DA@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
On Fri, Aug 25, 2023 at 12:25:18AM +0800, Shengyu Qu wrote:
> Add SPL version of SYS_MALLOC_CLEAR_ON_INIT, this would help devices
> that need to clear ram before use to work correctly.
>
> Signed-off-by: Bo Gan <ganboing@gmail.com>
> Signed-off-by: Shengyu Qu <wiagn233@outlook.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-08-24 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230824162521.22240-1-wiagn233@outlook.com>
2023-08-24 16:25 ` [PATCH v6 1/4] Kconfig: Add SPL_SYS_MALLOC_CLEAR_ON_INIT Shengyu Qu
2023-08-24 16:31 ` Tom Rini [this message]
2023-08-24 16:25 ` [PATCH v6 2/4] dlmalloc: Add support for SPL_SYS_MALLOC_CLEAR_ON_INIT Shengyu Qu
2023-08-24 16:25 ` [PATCH v6 3/4] riscv: cpu: jh7110: Imply SPL_SYS_MALLOC_CLEAR_ON_INIT Shengyu Qu
2023-09-04 6:24 ` Leo Liang
2023-08-24 16:25 ` [PATCH v6 4/4] configs: starfive: Disable SYS_MALLOC_CLEAR_ON_INIT by default Shengyu Qu
2023-09-04 6:28 ` 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=20230824163123.GC3953269@bill-the-cat \
--to=trini@konsulko.com \
--cc=andre.przywara@arm.com \
--cc=bmeng@tinylab.org \
--cc=ganboing@gmail.com \
--cc=jbx6244@gmail.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=michal.simek@amd.com \
--cc=minda.chen@starfivetech.com \
--cc=rick@andestech.com \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=wiagn233@outlook.com \
--cc=xypron.glpk@gmx.de \
--cc=yanhong.wang@starfivetech.com \
--cc=ycliang@andestech.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