common: print \n in initr_scsi()

[u-boot] / test / README

diff --git a/test/README b/test/README
index ee559729b0b78b1604d06cd7f15f9310b3f7d127..873a4e1931325ab1d56dc4d8b34c2429344d2b80 100644 (file)
--- a/test/README
+++ b/test/README
@@ -13,7 +13,7 @@ To run most tests on sandbox, type this:
     test/run
 
 in the U-Boot directory. Note that only the pytest suite is run using this
-comment.
+command.
 
 
 Sandbox
@@ -29,7 +29,7 @@ Pytest Suite
 Many tests are available using the pytest suite, in test/py. This can run
 either on sandbox or on real hardware. It relies on the U-Boot console to
 inject test commands and check the result. It is slower to run than C code,
-but provides the ability to unify lots of test and summarise their results.
+but provides the ability to unify lots of tests and summarise their results.
 
 You can run the tests on sandbox with:
 
@@ -46,7 +46,7 @@ tbot
 Tbot provides a way to execute tests on target hardware. It is intended for
 trying out both U-Boot and Linux (and potentially other software) on a
 number of boards automatically. It can be used to create a continuous test
-environment. See tools/tbot/README for more information.
+environment. See http://www.tbot.tools for more information.
 
 
 Ad-hoc tests
@@ -55,11 +55,11 @@ Ad-hoc tests
 There are several ad-hoc tests which run outside the pytest environment:
 
    test/fs     - File system test (shell script)
-   test/image  - FIT and lagacy image tests (shell script and Python)
+   test/image  - FIT and legacy image tests (shell script and Python)
    test/stdint - A test that stdint.h can be used in U-Boot (shell script)
    trace       - Test for the tracing feature (shell script)
 
-The above should be converted to run as part of the pytest suite.
+TODO: Move these into pytest.
 
 
 When to write tests