From 11da3403e91c9f510495c75d07750b6ac3c3b2e7 Mon Sep 17 00:00:00 2001 From: Tom Rini Date: Fri, 24 Oct 2025 10:02:57 -0600 Subject: doc: usage: Add general rule for `$?` For nearly all commands in U-Boot the '?' variable is handled the same way with 0 meaning success, 1 meaning any failure. Explain this in the general rules section of the cmdline documentation (with a link to a counter example) and then remove the redundant wording from most commands. We retain a section about the return value in a number of places where we are doing something such as always returning a specific value or we have useful additional information to go along with the normal return codes. Signed-off-by: Tom Rini Reviewed-by: Heinrich Schuchardt --- doc/usage/cmd/source.rst | 6 ------ 1 file changed, 6 deletions(-) (limited to 'doc/usage/cmd/source.rst') diff --git a/doc/usage/cmd/source.rst b/doc/usage/cmd/source.rst index 0de5f33390e..bd585f37414 100644 --- a/doc/usage/cmd/source.rst +++ b/doc/usage/cmd/source.rst @@ -188,9 +188,3 @@ The FIT image file format requires CONFIG_FIT=y.# The legacy U-Boot image file format requires CONFIG_LEGACY_IMAGE_FORMAT=y. On hardened systems support for the legacy U-Boot image format should be disabled as these images cannot be signed and verified. - -Return value ------------- - -If the scripts is executed successfully, the return value $? is 0 (true). -Otherwise it is 1 (false). -- cgit v1.2.3