From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/2] README: Add more clarification about CONFIG_SYS_SPL_MALLOC_START
Date: Thu, 12 Nov 2015 14:41:45 +0100 [thread overview]
Message-ID: <20151112144145.3538edbd@lilith> (raw)
In-Reply-To: <1447333811-31720-2-git-send-email-fabio.estevam@freescale.com>
Hello Fabio,
On Thu, 12 Nov 2015 11:10:11 -0200, Fabio Estevam
<fabio.estevam@freescale.com> wrote:
> Add some text to clarify the usage of full malloc (when
> CONFIG_SYS_SPL_MALLOC_START is selected) and also that simple malloc()
> can be used prior to DRAM initialization if CONFIG_SYS_MALLOC_F is defined.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> Changes since v1:
> - Improve README and commit log (Simon)
Not sure why you made this a 2-patch series -- a single patch would
have been fine.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2015-11-12 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 13:10 [U-Boot] [PATCH v2 1/2] board_init: Change the logic to setup malloc_base Fabio Estevam
2015-11-12 13:10 ` [U-Boot] [PATCH v2 2/2] README: Add more clarification about CONFIG_SYS_SPL_MALLOC_START Fabio Estevam
2015-11-12 13:41 ` Albert ARIBAUD [this message]
2015-11-12 14:29 ` Tom Rini
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=20151112144145.3538edbd@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.