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/setexpr.rst | 7 ------- 1 file changed, 7 deletions(-) (limited to 'doc/usage/cmd/setexpr.rst') diff --git a/doc/usage/cmd/setexpr.rst b/doc/usage/cmd/setexpr.rst index 5bc37ae50fc..96894a2754f 100644 --- a/doc/usage/cmd/setexpr.rst +++ b/doc/usage/cmd/setexpr.rst @@ -147,10 +147,3 @@ Configuration * The *setexpr gsub* and *setexpr sub* sub-commands are only available if CONFIG_REGEX=y. For an overview of the supported regex syntax, see :doc:`test`. - -Return value ------------- - -The return value $? is set to 0 (true) if the operation was successful. - -If an error occurs, the return value $? is set to 1 (false). -- cgit v1.2.3