From: Bin Meng <bmeng.cn@gmail.com>
To: tekkamanv@163.com
Cc: "U-Boot Mailing List" <u-boot@lists.denx.de>,
"Simon Glass" <sjg@chromium.org>,
"Marek Behún" <marek.behun@nic.cz>,
"Amit Singh Tomar" <amittomer25@gmail.com>,
"Matthias Brugger" <mbrugger@suse.com>,
"Alexandru Gagniuc" <mr.nuke.me@gmail.co>,
jaeckel-floss@eyet-services.de, klaus@linux.vnet.ibm.com,
"Heinrich Schuchardt" <xypron.glpk@gmx.de>,
tekkamanv@starfivetech.com, tekkamanninja@163.com
Subject: Re: [PATCH 1/2] riscv: Enable SYS_MALLOC_LEN config
Date: Sat, 2 Oct 2021 22:15:35 +0800 [thread overview]
Message-ID: <CAEUhbmXPuHaO=vFqnNRw43G3AVZ2+Lb+FrR3M1p57=3KVUstEg@mail.gmail.com> (raw)
In-Reply-To: <20210930120516.449450-2-tekkamanv@163.com>
On Thu, Sep 30, 2021 at 8:07 PM <tekkamanv@163.com> wrote:
>
> From: TekkamanV <tekkamanv@starfivetech.com>
>
Please add a commit message.
> Signed-off-by: TekkamanV <tekkamanv@starfivetech.com>
> ---
> Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Kconfig b/Kconfig
> index a6c42b902f..7f63929c60 100644
> --- a/Kconfig
> +++ b/Kconfig
> @@ -249,7 +249,7 @@ config SYS_MALLOC_F_LEN
>
> config SYS_MALLOC_LEN
> hex "Define memory for Dynamic allocation"
> - depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP || ARCH_ROCKCHIP
> + depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP || ARCH_ROCKCHIP || RISCV
You need to also migrate existing RISC-V boards to Kconfig, by
removing CONFIG_SYS_MALLOC_LEN from their config.h files.
> default 0x2000000 if ARCH_ROCKCHIP
> help
> This defines memory to be allocated for Dynamic allocation
Regards,
Bin
next prev parent reply other threads:[~2021-10-02 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 12:05 [PATCH 0/2] riscv: Enable some configs in the Kconfig tekkamanv
2021-09-30 12:05 ` [PATCH 1/2] riscv: Enable SYS_MALLOC_LEN config tekkamanv
2021-10-02 14:15 ` Bin Meng [this message]
2021-09-30 12:05 ` [PATCH 2/2] riscv: Enable SYS_CLK_FREQ config tekkamanv
2021-10-02 14:16 ` Bin Meng
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='CAEUhbmXPuHaO=vFqnNRw43G3AVZ2+Lb+FrR3M1p57=3KVUstEg@mail.gmail.com' \
--to=bmeng.cn@gmail.com \
--cc=amittomer25@gmail.com \
--cc=jaeckel-floss@eyet-services.de \
--cc=klaus@linux.vnet.ibm.com \
--cc=marek.behun@nic.cz \
--cc=mbrugger@suse.com \
--cc=mr.nuke.me@gmail.co \
--cc=sjg@chromium.org \
--cc=tekkamanninja@163.com \
--cc=tekkamanv@163.com \
--cc=tekkamanv@starfivetech.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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 NNTP newsgroup(s).