forked from OERV-BSP/u-boot
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 <trini@konsulko.com> Reviewed-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
This commit is contained in:
@@ -223,9 +223,3 @@ This shows looking at a device with multiple partition tables::
|
||||
type: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
|
||||
guid: a0891d7e-b930-4513-94da-f629dbd637b2
|
||||
=>
|
||||
|
||||
Return value
|
||||
------------
|
||||
|
||||
The return value $? is set to 0 (true) if the command succededd. If an
|
||||
error occurs, the return value $? is set to 1 (false).
|
||||
|
||||
Reference in New Issue
Block a user