diff options
| author | David Lechner <[email protected]> | 2025-11-21 11:36:49 -0600 |
|---|---|---|
| committer | Heinrich Schuchardt <[email protected]> | 2025-11-21 19:29:23 +0100 |
| commit | fff78d3bb25dc0c4b20b4ab9908cb355f5808178 (patch) | |
| tree | 949504975745ed37bc3d60535b9ce17fb984c2d8 /doc/develop | |
| parent | a5dc935df7d0e5df4072521ba23279d07bbadcb5 (diff) | |
doc: pytest: fix u-boot-test-flash typo
Fix typo: `s/u-boot-test-flash1/u-boot-test-flash/`. The correct name of
the script doesn't have a "1" in it.
Signed-off-by: David Lechner <[email protected]>
Reviewed-by: Heinrich Schuchardt <[email protected]>
Diffstat (limited to 'doc/develop')
| -rw-r--r-- | doc/develop/pytest/usage.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/develop/pytest/usage.rst b/doc/develop/pytest/usage.rst index 800a0323d0a..7335a39b963 100644 --- a/doc/develop/pytest/usage.rst +++ b/doc/develop/pytest/usage.rst @@ -392,7 +392,7 @@ to flash, pulsing the board's reset signal is likely all this script needs to do. However, in some scenarios, this script may perform other actions. For example, it may call out to some SoC- or board-specific vendor utility in order to download the U-Boot binary directly into RAM and execute it. This would -avoid the need for ``u-boot-test-flash1`` to actually write U-Boot to flash, +avoid the need for ``u-boot-test-flash`` to actually write U-Boot to flash, thus saving wear on the flash chip(s). u-boot-test-release |