From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Workflows <workflows@vger.kernel.org>,
Linux Kernel Selftests <linux-kselftest@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Bagas Sanjaya <bagasdotme@gmail.com>,
David Gow <davidgow@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Tim Bird <Tim.Bird@sony.com>, Rae Moar <rmoar@google.com>
Subject: [PATCH 2/2] Documentation: ktap: Separate first bullet list items
Date: Thu, 14 Aug 2025 08:20:46 +0700 [thread overview]
Message-ID: <20250814012046.21235-3-bagasdotme@gmail.com> (raw)
In-Reply-To: <20250814012046.21235-1-bagasdotme@gmail.com>
The first bullet list items are shown in htmldocs output as combined
with previous paragraph due to missing blank line separator. Add it.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/dev-tools/ktap.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/dev-tools/ktap.rst b/Documentation/dev-tools/ktap.rst
index 54fac3d3bf7b05..a9810bed5fd4de 100644
--- a/Documentation/dev-tools/ktap.rst
+++ b/Documentation/dev-tools/ktap.rst
@@ -20,6 +20,7 @@ machine-readable, whereas the diagnostic data is unstructured and is there to
aid human debugging.
KTAP output is built from four different types of lines:
+
- Version lines
- Plan lines
- Test case result lines
@@ -38,6 +39,7 @@ All KTAP-formatted results begin with a "version line" which specifies which
version of the (K)TAP standard the result is compliant with.
For example:
+
- "KTAP version 1"
- "TAP version 13"
- "TAP version 14"
@@ -276,6 +278,7 @@ Example KTAP output
This output defines the following hierarchy:
A single test called "main_test", which fails, and has three subtests:
+
- "example_test_1", which passes, and has one subtest:
- "test_1", which passes, and outputs the diagnostic message "test_1: initializing test_1"
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-08-14 1:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 1:20 [PATCH 0/2] Documentation: ktap: formatting cleanup Bagas Sanjaya
2025-08-14 1:20 ` [PATCH 1/2] Documentation: ktap: Correct "its" spelling Bagas Sanjaya
2025-08-14 1:20 ` Bagas Sanjaya [this message]
2025-08-14 1:58 ` [PATCH 0/2] Documentation: ktap: formatting cleanup Randy Dunlap
2025-08-14 6:39 ` Bagas Sanjaya
2025-08-14 15:55 ` Randy Dunlap
2025-08-14 22:55 ` Bagas Sanjaya
2025-08-18 16:29 ` Jonathan Corbet
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=20250814012046.21235-3-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=Tim.Bird@sony.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rmoar@google.com \
--cc=skhan@linuxfoundation.org \
--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