From: Stephen Kitt <steve@sk2.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] docs: add a script to check sysctl docs
Date: Thu, 27 Feb 2020 22:58:57 +0100 [thread overview]
Message-ID: <20200227225857.2339e365@heffalump.sk2.org> (raw)
In-Reply-To: <20200225033710.312450f6@lwn.net>
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
On Tue, 25 Feb 2020 03:37:10 -0700, Jonathan Corbet <corbet@lwn.net> wrote:
> On Wed, 19 Feb 2020 16:34:42 +0100
> Stephen Kitt <steve@sk2.org> wrote:
>
> > This script allows sysctl documentation to be checked against the
> > kernel source code, to identify missing or obsolete entries. Running
> > it against 5.5 shows for example that sysctl/kernel.rst has two
> > obsolete entries and is missing 52 entries.
> >
> > Signed-off-by: Stephen Kitt <steve@sk2.org>
> > ---
> > Changes since v2:
> > * drop UTF-8 characters
> > * fix license identifier
> > * fix example invocation to include path as well as table
> >
> > v2 was the initial submission (in v2 of the sysctl/kernel.rst patch
> > set).
>
> This seems like a useful thing to have, so I've applied it. It would be
> rather more useful, though, with a bit of ... wait for it ...
> documentation. Even just an example command line in the header comments
> would be a good place to start. Care to send a followup? :)
The committed script has this:
+# Example invocation:
+# scripts/check-sysctl-docs -vtable="kernel" \
+# Documentation/admin-guide/sysctl/kernel.rst \
+# $(git grep -l register_sysctl_)
+#
+# Specify -vdebug=1 to see debugging information
but I agree that it needs more documentation ;-). In particular, I need to
explain what the script expects in terms of document layout...
Where would be the best place? In admin-guide/sysctl/index.rst, as a “how to
maintain these files” section, or in a separate document, or in the script
headers?
Regards,
Stephen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-02-28 1:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 15:34 [PATCH v3] docs: add a script to check sysctl docs Stephen Kitt
2020-02-25 10:37 ` Jonathan Corbet
2020-02-27 21:58 ` Stephen Kitt [this message]
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=20200227225857.2339e365@heffalump.sk2.org \
--to=steve@sk2.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@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;
as well as URLs for NNTP newsgroup(s).