From: Marek Vasut <marek.vasut@mailbox.org>
To: Philip Oberfichtner <pro@denx.de>, u-boot@lists.denx.de
Cc: Andre Przywara <andre.przywara@arm.com>,
Anshul Dalal <anshuld@ti.com>,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Greg Malysa <malysagreg@gmail.com>,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Jerome Forissier <jerome.forissier@linaro.org>,
Nathan Barrett-Morrison <nathan.morrison@timesys.com>,
Peng Fan <peng.fan@nxp.com>, Simon Glass <sjg@chromium.org>,
Tom Rini <trini@konsulko.com>,
Trevor Woerner <twoerner@gmail.com>, Ye Li <ye.li@nxp.com>
Subject: Re: [PATCH v5 2/3] Image size checks: Clarify help texts
Date: Wed, 31 Dec 2025 22:20:58 +0100 [thread overview]
Message-ID: <4f35fb8a-51dc-4fd3-afbe-8f7e7f51150e@mailbox.org> (raw)
In-Reply-To: <20251110091256.2422534-3-pro@denx.de>
On 11/10/25 10:12 AM, Philip Oberfichtner wrote:
> Adapt help texts for CONFIG_XXX_SIZE_LIMITs to their new logic.
>
> Signed-off-by: Philip Oberfichtner <pro@denx.de>
Reviewed-by: Marek Vasut <marek.vasut@mailbox.org>
next prev parent reply other threads:[~2025-12-31 21:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 9:12 [PATCH v5 0/3] Harmonize image size checks Philip Oberfichtner
2025-11-10 9:12 ` [PATCH v5 1/3] Image size checks: Use HAS_SIZE_LIMIT consistently Philip Oberfichtner
2025-12-31 21:27 ` Marek Vasut
2026-01-07 17:34 ` Philip Oberfichtner
2025-11-10 9:12 ` [PATCH v5 2/3] Image size checks: Clarify help texts Philip Oberfichtner
2025-12-31 21:20 ` Marek Vasut [this message]
2025-11-10 9:12 ` [PATCH v5 3/3] Makefile: Deduplicate image size checks Philip Oberfichtner
2025-12-31 21:25 ` Marek Vasut
2025-12-01 18:30 ` [PATCH v5 0/3] Harmonize " Philip Oberfichtner
2025-12-01 18:37 ` Tom Rini
2025-12-01 18:38 ` Philip Oberfichtner
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=4f35fb8a-51dc-4fd3-afbe-8f7e7f51150e@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=andre.przywara@arm.com \
--cc=anshuld@ti.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=malysagreg@gmail.com \
--cc=nathan.morrison@timesys.com \
--cc=peng.fan@nxp.com \
--cc=pro@denx.de \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=twoerner@gmail.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 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.