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/cli.rst | 5 ----- 1 file changed, 5 deletions(-) (limited to 'doc/usage/cmd/cli.rst') diff --git a/doc/usage/cmd/cli.rst b/doc/usage/cmd/cli.rst index 23e5ee7a902..97de5331d1b 100644 --- a/doc/usage/cmd/cli.rst +++ b/doc/usage/cmd/cli.rst @@ -70,8 +70,3 @@ compiled:: modern => cli set old Want to set current parser to old, but its code was not compiled! - -Return value ------------- - -The return value $? indicates whether the command succeeded. -- cgit v1.2.3