public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Leo Liang <ycliang@andestech.com>
To: Shengyu Qu <wiagn233@outlook.com>
Cc: <rick@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 4/4] configs: starfive: Disable SYS_MALLOC_CLEAR_ON_INIT by default
Date: Mon, 4 Sep 2023 14:28:43 +0800	[thread overview]
Message-ID: <ZPV5G9D0ioO1OAS3@swlinux02> (raw)
In-Reply-To: <TY3P286MB2611C8919347A7E4B420FF54981DA@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>

On Fri, Aug 25, 2023 at 12:25:21AM +0800, Shengyu Qu wrote:
> SPL_SYS_MALLOC_CLEAR_ON_INIT would enable SYS_MALLOC_CLEAR_ON_INIT by
> default, but that's not need on JH7110, so disable that.
> 
> Signed-off-by: Shengyu Qu <wiagn233@outlook.com>
> ---
>  configs/starfive_visionfive2_defconfig | 2 ++
>  1 file changed, 2 insertions(+)

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

      reply	other threads:[~2023-09-04  6:30 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
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 [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=ZPV5G9D0ioO1OAS3@swlinux02 \
    --to=ycliang@andestech.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 \
    /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