On 9/3/25 12:56 PM, Philip Oberfichtner wrote:
The multiple XXX_SIZE_LIMIT options use slightly varying help texts.
Their similarities and differences should become more clear if we use
consistent help texts.
Signed-off-by: Philip Oberfichtner <p...@denx.de>
---
Kconfig | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/Kconfig b/Kconfig
index e73dd91a408..aa00669ba20 100644
--- a/Kconfig
+++ b/Kconfig
@@ -538,7 +538,7 @@ config BUILD_TARGET
menu "Image size limits"
config HAS_BOARD_SIZE_LIMIT
- bool "Define a maximum size for the U-Boot image"
+ bool "Enable size limit check for the U-Boot image"
depends on !COMPILE_TEST
default y if RCAR_32 || RCAR_64
help
@@ -562,11 +562,11 @@ config HAS_VPL_SIZE_LIMIT
depends on VPL
config VPL_SIZE_LIMIT
- hex "Maximum size of VPL image"
+ hex "Maximum size of VPL image in bytes"
depends on HAS_VPL_SIZE_LIMIT
help
- Specifies the maximum length of the U-Boot VPL image.
- If this value is zero, it is ignored.
+ Maximum size of the VPL image. When defined, the build system checks
The "when defined ..." part should be in HAS_VPL_SIZE_LIMIT , which
gates access to VPL_SIZE_LIMIT . If HAS_VPL_SIZE_LIMIT is set, then this
is always defined.
