Skip to contentSkip to conversation

Documentation: kselftest: fix codeblock

PATCH In review Yo-Jung (Leo) Lin 2 participants 2 messages Apr 29, 2024 – May 3, 2024

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Documentation: kselftest: fix codeblock

Add extra colon to mark command in the next paragraph as codeblock

---
 Documentation/dev-tools/kselftest.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/dev-tools/kselftest.rst +1 -1
index ff10dc6eef5d..dcf634e411bd 100644
@@ -183,7 +183,7 @@ expected time it takes to run a test. If you have control over the systems
 which will run the tests you can configure a test runner on those systems to
 use a greater or lower timeout on the command line as with the `-o` or
 the `--override-timeout` argument. For example to use 165 seconds instead
-one would use:
+one would use::
 
    $ ./run_kselftest.sh --override-timeout 165
 
Signature · 1 line
2.34.1
maintainer
#1 lore raw
Quoted 12 lines · Yo-Jung (Leo) Lin

Add extra colon to mark command in the next paragraph as codeblock

---
  Documentation/dev-tools/kselftest.rst | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/dev-tools/kselftest.rst +0 -0
index ff10dc6eef5d..dcf634e411bd 100644

Documentation/dev-tools/kselftest.rst expected time it takes to run a test. If you have control over the systems · line 189

Quoted 8 lines
Documentation/dev-tools/kselftest.rst +1 -1
@@ -183,7 +183,7 @@ expected time it takes to run a test. If you have control over the systems
  which will run the tests you can configure a test runner on those systems to
  use a greater or lower timeout on the command line as with the `-o` or
  the `--override-timeout` argument. For example to use 165 seconds instead
-one would use:
+one would use::
 
     $ ./run_kselftest.sh --override-timeout 165
 

Thank you. Applied to linux=kselftest next for Linux 6.10-rc1.

thanks,
-- Shuah