The GNU target-tuple prefixes shown in the CROSS_COMPILE examples are
missing their trailing dash.
Fixes: 46201d47d6c4 ("Documentation: kunit: Reorganize documentation related to
running tests")
Fixes: 957063874c76 ("Documentation: kunit: Add CLI args for kunit_tool")
Assisted-by: LLM
Signed-off-by: Karl Mehltretter <[email protected]>
---
Documentation/dev-tools/kunit/run_wrapper.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/dev-tools/kunit/run_wrapper.rst
b/Documentation/dev-tools/kunit/run_wrapper.rst
index cecc110a3399f..9221acddf3fa8 100644
--- a/Documentation/dev-tools/kunit/run_wrapper.rst
+++ b/Documentation/dev-tools/kunit/run_wrapper.rst
@@ -189,10 +189,10 @@ via UML. To run tests on qemu, by default it requires two
flags:
Kbuild. As a reminder, this will be the prefix for the toolchain
binaries such as GCC. For example:
- - ``sparc64-linux-gnu`` if we have the sparc toolchain installed on
+ - ``sparc64-linux-gnu-`` if we have the sparc toolchain installed on
our system.
- -
``$HOME/toolchains/microblaze/gcc-9.2.0-nolibc/microblaze-linux/bin/microblaze-linux``
+ -
``$HOME/toolchains/microblaze/gcc-9.2.0-nolibc/microblaze-linux/bin/microblaze-linux-``
if we have downloaded the microblaze toolchain from the 0-day
website to a directory in our home directory called toolchains.
@@ -293,7 +293,7 @@ command line arguments:
- ``sparc64-linux-gnu-`` if we have the sparc toolchain installed on
our system.
- -
``$HOME/toolchains/microblaze/gcc-9.2.0-nolibc/microblaze-linux/bin/microblaze-linux``
+ -
``$HOME/toolchains/microblaze/gcc-9.2.0-nolibc/microblaze-linux/bin/microblaze-linux-``
if we have downloaded the microblaze toolchain from the 0-day
website to a specified path in our home directory called toolchains.
--
2.53.0
