From: Ian Campbell <ijc+uboot@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] sunxi: Set SYS_MALLOC_CLEAR_ON_INIT to n
Date: Sat, 09 May 2015 14:48:07 +0100 [thread overview]
Message-ID: <1431179287.15640.303.camel@hellion.org.uk> (raw)
In-Reply-To: <1430824867-10682-1-git-send-email-hdegoede@redhat.com>
On Tue, 2015-05-05 at 13:21 +0200, Hans de Goede wrote:
> We don't need this on sunxi,
Please say why here. I assume something like "we always use calloc or
memset when initialised memory is required"?
> and not having is shaves some time of out boot
> time.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
With that added:
Acked-by: Ian Campbell <ijc@hellion.org.uk>
prev parent reply other threads:[~2015-05-09 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 11:21 [U-Boot] [PATCH 1/2] sunxi: Set SYS_MALLOC_CLEAR_ON_INIT to n Hans de Goede
2015-05-05 11:21 ` [U-Boot] [PATCH 2/2] console: Fix pre-console flushing via cfb_console being very slow Hans de Goede
2015-05-09 13:49 ` Ian Campbell
2015-05-09 15:53 ` Hans de Goede
2015-05-10 14:07 ` Tom Rini
2015-05-09 13:48 ` Ian Campbell [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=1431179287.15640.303.camel@hellion.org.uk \
--to=ijc+uboot@hellion.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox