From: Francesco Dolcini <francesco@dolcini.it>
To: max.oss.09@gmail.com
Cc: u-boot@lists.denx.de,
"Max Krummenacher" <max.krummenacher@toradex.com>,
"Alice Guo" <alice.guo@nxp.com>,
"Emanuele Ghidoli" <emanuele.ghidoli@toradex.com>,
"Ernest Van Hoecke" <ernest.vanhoecke@toradex.com>,
"Francesco Dolcini" <francesco.dolcini@toradex.com>,
"João Paulo Gonçalves" <joao.goncalves@toradex.com>,
"Marek Vasut" <marek.vasut+renesas@mailbox.org>,
"Peng Fan" <peng.fan@nxp.com>, "Tom Rini" <trini@konsulko.com>,
"Ye Li" <ye.li@nxp.com>
Subject: Re: [PATCH] configs: toradex-smarc-imx95: set spl_stack
Date: Wed, 26 Nov 2025 15:03:40 +0100 [thread overview]
Message-ID: <20251126140340.GA45401@francesco-nb> (raw)
In-Reply-To: <20251126134107.2969608-1-max.oss.09@gmail.com>
On Wed, Nov 26, 2025 at 02:41:04PM +0100, max.oss.09@gmail.com wrote:
> From: Max Krummenacher <max.krummenacher@toradex.com>
>
> The SPL_STACK config option now depends on having SPL_HAVE_INIT_STACK
> defined. This made savedefconfig dropping SPL_STACK when sending the
> initial configuration.
> Note that SPL/U-Boot are able to boot linux from mass storage with
> SPL_STACK not set but other use cases might run out of stack or
> overlap with other RAM use.
>
> Compare with:
> commit d6a53f523afe ("spl: Add an SPL_HAVE_INIT_STACK option")
> commit 25fefa05d732 ("configs: Resync with savedefconfig")
>
> Fixes: ff0540fcfe49 ("board: toradex: add Toradex SMARC iMX95")
> Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Acked-by: Francesco Dolcini <francesco.dolcini@toradex.com>
next prev parent reply other threads:[~2025-11-26 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 13:41 [PATCH] configs: toradex-smarc-imx95: set spl_stack max.oss.09
2025-11-26 14:03 ` Francesco Dolcini [this message]
2025-11-27 17:25 ` Fabio Estevam
2025-11-27 18:41 ` 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=20251126140340.GA45401@francesco-nb \
--to=francesco@dolcini.it \
--cc=alice.guo@nxp.com \
--cc=emanuele.ghidoli@toradex.com \
--cc=ernest.vanhoecke@toradex.com \
--cc=francesco.dolcini@toradex.com \
--cc=joao.goncalves@toradex.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=max.krummenacher@toradex.com \
--cc=max.oss.09@gmail.com \
--cc=peng.fan@nxp.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ye.li@nxp.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