From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] env_mmc: avoid stack allocation for env
Date: Sat, 9 May 2015 00:15:37 +0200 [thread overview]
Message-ID: <201505090015.37722.marex@denx.de> (raw)
In-Reply-To: <1431121896-2677-1-git-send-email-tharvey@gateworks.com>
On Friday, May 08, 2015 at 11:51:36 PM, Tim Harvey wrote:
> Allocating space for temporary env on the stack makes env_relocate_spec()
> unsuitable for SPL environments which have very little stack.
Well yeah, but what if you don't have malloc area ? I'd expect that
the be the case in SPL quite often.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-05-08 22:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 21:51 [U-Boot] [PATCH] env_mmc: avoid stack allocation for env Tim Harvey
2015-05-08 22:15 ` Marek Vasut [this message]
2015-05-08 23:14 ` Tom Rini
2015-05-11 19:08 ` Tim Harvey
2015-05-12 15:14 ` Tom Rini
2015-05-13 19:58 ` Tim Harvey
2015-05-13 22:40 ` Tim Harvey
2015-05-14 2:02 ` Simon Glass
2015-05-14 3:22 ` Simon Glass
2015-05-14 13:11 ` Tim Harvey
2015-08-02 21:29 ` Simon Glass
2015-05-11 19:02 ` Tim Harvey
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=201505090015.37722.marex@denx.de \
--to=marex@denx.de \
--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