From: Philip Oberfichtner <pro@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
Paul Kocialkowski <contact@paulk.fr>,
Oliver Gaskell <Oliver.Gaskell@analog.com>,
Greg Malysa <malysagreg@gmail.com>,
Nathan Barrett-Morrison <nathan.morrison@timesys.com>,
Trevor Woerner <twoerner@gmail.com>, Marek Vasut <marex@denx.de>,
Jerome Forissier <jerome.forissier@linaro.org>,
Paul Barker <paul.barker.ct@bp.renesas.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 1/1] Kconfig: typo restict
Date: Thu, 31 Jul 2025 13:45:15 +0200 [thread overview]
Message-ID: <aItXSz1FcmATTYQe@antares> (raw)
In-Reply-To: <aIoxIl6rdyN3NbNc@antares>
On Wed, Jul 30, 2025 at 04:50:15PM +0200, Philip Oberfichtner wrote:
> > > With VPL_SIZE_LIMIT and a patch for UBOOT_WITH_SPL_SIZE_LIMIT pending things
> > > get even more involved.
> > >
> > > We should think about a documentation page on size limits:
> > >
> > > CONFIG_HAS_BOARD_SIZE_LIMIT
> > > CONFIG_BOARD_SIZE_LIMIT
> > > CONFIG_SPL_SIZE_LIMIT
> > > CONFIG_SPL_SIZE_LIMIT_SUBTRACT_GD
> > > CONFIG_SPL_SIZE_LIMIT_SUBTRACT_MALLOC
> > > CONFIG_SPL_SIZE_LIMIT_PROVIDE_STACK
> > > CONFIG_TPL_SIZE_LIMIT
> > > CONFIG_VPL_SIZE_LIMIT
> >
Hi again,
> > As Philip has hit adding a new MIPS board and need for specific size
> > check, yes, better documentation (and then perhaps adjusting and
> > cleanup) of our various size checks is much needed and would be
> > appreciated.
I just posted an RFC on how we might want to start cleaning up the
current situation:
https://patchwork.ozlabs.org/project/uboot/list/?series=467406
Best,
Philip
next prev parent reply other threads:[~2025-07-31 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 12:54 [PATCH 1/1] Kconfig: typo restict Heinrich Schuchardt
2025-07-30 12:58 ` Quentin Schulz
2025-07-30 13:05 ` Heinrich Schuchardt
2025-07-30 14:32 ` Tom Rini
2025-07-30 14:50 ` Philip Oberfichtner
2025-07-31 11:45 ` Philip Oberfichtner [this message]
2025-08-05 1: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=aItXSz1FcmATTYQe@antares \
--to=pro@denx.de \
--cc=Oliver.Gaskell@analog.com \
--cc=contact@paulk.fr \
--cc=heinrich.schuchardt@canonical.com \
--cc=jerome.forissier@linaro.org \
--cc=malysagreg@gmail.com \
--cc=marex@denx.de \
--cc=nathan.morrison@timesys.com \
--cc=paul.barker.ct@bp.renesas.com \
--cc=quentin.schulz@cherry.de \
--cc=trini@konsulko.com \
--cc=twoerner@gmail.com \
--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.