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:
@@ -79,8 +79,3 @@ after which an ACK response is required. The window size defaults to 1.
|
||||
|
||||
If CONFIG_TFTP_TSIZE=y, the progress bar is limited to 50 '#' characters.
|
||||
Otherwise an '#' is written per UDP package which may decrease performance.
|
||||
|
||||
Return value
|
||||
------------
|
||||
|
||||
The return value $? is 0 (true) on success and 1 (false) otherwise.
|
||||
|
||||
Reference in New Issue
Block a user