From: "Tomasz Warniełło" <tomasz.warniello@gmail.com>
To: corbet@lwn.net
Cc: "Tomasz Warniełło" <tomasz.warniello@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 02/15] scripts: kernel-doc: Transform documentation into POD (2/15)
Date: Mon, 3 Jan 2022 05:43:35 +0100 [thread overview]
Message-ID: <20220103044338.506244-2-tomasz.warniello@gmail.com> (raw)
In-Reply-To: <20220103044338.506244-1-tomasz.warniello@gmail.com>
Step 2) Add the SYNOPSIS section
Rst-only options are grouped around rst, the rest is arranged
as in the OPTIONS susections (yet to be translated into POD,
check at the end of the series).
See step 1 for the series details.
Signed-off-by: Tomasz Warniełło <tomasz.warniello@gmail.com>
---
scripts/kernel-doc | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/scripts/kernel-doc b/scripts/kernel-doc
index 46d3e779bf5d..c8fbf1d3d5aa 100755
--- a/scripts/kernel-doc
+++ b/scripts/kernel-doc
@@ -20,6 +20,25 @@ use strict;
kernel-doc - Print formatted kernel documentation to stdout
+=head1 SYNOPSIS
+
+ kernel-doc [-h] [-v] [-Werror]
+ [ -man |
+ -rst [-sphinx-version VERSION] [-enable-lineno] |
+ -none
+ ]
+ [
+ -export |
+ -internal |
+ [-function NAME] ... |
+ [-nosymbol NAME] ...
+ ]
+ [-no-doc-sections]
+ [-export-file FILE] ...
+ FILE ...
+
+Run `kernel-doc -h` for details.
+
=cut
# 18/01/2001 - Cleanups
--
2.30.2
next prev parent reply other threads:[~2022-01-03 4:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 4:43 [PATCH v2 01/15] scripts: kernel-doc: Transform documentation into POD (1/15) Tomasz Warniełło
2022-01-03 4:43 ` Tomasz Warniełło [this message]
2022-01-03 4:43 ` [PATCH v2 03/15] scripts: kernel-doc: Transform documentation into POD (3/15) Tomasz Warniełło
2022-01-03 4:43 ` [PATCH v2 04/15] scripts: kernel-doc: Transform documentation into POD (4/15) Tomasz Warniełło
2022-01-03 4:43 ` [PATCH v2 05/15] scripts: kernel-doc: Transform documentation into POD (5/15) Tomasz Warniełło
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=20220103044338.506244-2-tomasz.warniello@gmail.com \
--to=tomasz.warniello@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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
Powered by JetHome