From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page sysfs.5
Date: Thu, 25 Dec 2025 14:17:25 +0100 [thread overview]
Message-ID: <aU03nbimYcA5kn8J@devuan> (raw)
In-Reply-To: <aUzjslUS92HiUBEI@meinfjell.helgefjelltest.de>
[-- Attachment #1: Type: text/plain, Size: 2910 bytes --]
Hi Helge,
On Thu, Dec 25, 2025 at 07:11:46AM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue: The 2nd sentence is incomplete
>
> "This directory contains one file for each module parameter, with each file "
> "containing the value of the corresponding parameter. Some of these files "
> "are writable, allowing the"
Huh!
That happened in
commit 6df684e0d3e9129d27d2f37a35226bacee92f62e
Author: Michael Kerrisk <mtk.manpages@gmail.com>
Date: Mon Sep 11 12:14:44 2017 +0200
sysfs.5: Various additions and improvements
Drawn from Documentation/filesystems/sysfs.txt, P. Mochel's OLS
paper, and some naive investigation.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
which contains
[...]
+.TP
+.I notes
+[To be documented]
+.TP
+.I parameters
+This directory contains one file for each module parameter,
+with each file containing the value of the corresponding parameter.
+Some of these files are writable, allowing the
+.TP
+.I sections
+This subdirectories contains files with information about module sections.
+This information is mainly used for debugging.
[...]
Luckily, there's another similar sentence in the same file:
$ grep -C2 allowing man/man5/sysfs.5
.B sysfs
filesystem are read-only,
but some files are writable, allowing kernel variables to be changed.
To avoid redundancy,
symbolic links are heavily used to connect entries across the filesystem tree.
--
This directory contains one file for each module parameter,
with each file containing the value of the corresponding parameter.
Some of these files are writable, allowing the
.TP
.I sections
It seems he wanted to write that. I'll apply this fix:
commit 318b197cd7cd76c05a753e467ac8468676f9f344 (HEAD -> contrib)
Author: Alejandro Colomar <alx@kernel.org>
Date: Thu Dec 25 14:14:30 2025 +0100
man/man5/sysfs.5: /sys/module/parameters: Fix incomplete sentence
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Fixes: 6df684e0d3e9 (2017-09-11; "sysfs.5: Various additions and improvements")
Signed-off-by: Alejandro Colomar <alx@kernel.org>
diff --git a/man/man5/sysfs.5 b/man/man5/sysfs.5
index c9dbab772..971b7aa32 100644
--- a/man/man5/sysfs.5
+++ b/man/man5/sysfs.5
@@ -239,7 +239,7 @@ .SS Files and directories
.I parameters
This directory contains one file for each module parameter,
with each file containing the value of the corresponding parameter.
-Some of these files are writable, allowing the
+Some of these files are writable, allowing the parameters to be changed.
.TP
.I sections
This subdirectories contains files with information about module sections.
Thanks for the report!
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-25 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 7:11 Issue in man page sysfs.5 Helge Kreutzmann
2025-12-25 13:17 ` Alejandro Colomar [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-25 7:13 Helge Kreutzmann
2025-12-25 13:07 ` Alejandro Colomar
2025-12-25 7:10 Helge Kreutzmann
2025-12-25 13:04 ` Alejandro Colomar
2025-12-24 14:38 Helge Kreutzmann
2025-12-25 13:42 ` Alejandro Colomar
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=aU03nbimYcA5kn8J@devuan \
--to=alx@kernel.org \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.com \
/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