From: Karl Mehltretter <kmehltretter@gmail.com>
To: Brendan Higgins <brendan.higgins@linux.dev>
Cc: "Karl Mehltretter" <kmehltretter@gmail.com>,
"David Gow" <david@davidgow.net>,
"Rae Moar" <raemoar63@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Tim Bird" <tim.bird@sony.com>,
"Harinder Singh" <sharinder@google.com>,
"Maíra Canal" <mairacanal@riseup.net>,
"Daniel Latypov" <dlatypov@google.com>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] docs: KUnit: Fix cross-compiler prefix examples
Date: Sat, 5 Sep 2026 04:51:26 +0200 [thread overview]
Message-ID: <20260905025126.83693-1-kmehltretter@gmail.com> (raw)
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 <kmehltretter@gmail.com>
---
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
next reply other threads:[~2026-09-05 2:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 2:51 Karl Mehltretter [this message]
2026-09-05 2:58 ` [PATCH] docs: KUnit: Fix cross-compiler prefix examples Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260905025126.83693-1-kmehltretter@gmail.com \
--to=kmehltretter@gmail.com \
--cc=brendan.higgins@linux.dev \
--cc=corbet@lwn.net \
--cc=david@davidgow.net \
--cc=dlatypov@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mairacanal@riseup.net \
--cc=raemoar63@gmail.com \
--cc=rdunlap@infradead.org \
--cc=sharinder@google.com \
--cc=skhan@linuxfoundation.org \
--cc=tim.bird@sony.com \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox