From: Zenghui Yu <zenghui.yu@linux.dev>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: openipmi-developer@lists.sourceforge.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
corey@minyard.net, corbet@lwn.net, skhan@linuxfoundation.org
Subject: Re: [PATCH] docs: ipmi: Fix path of the "hotmod" module parameter
Date: Sun, 21 Jun 2026 07:06:04 +0800 [thread overview]
Message-ID: <54430fa8-00ac-47b7-a8e1-b2843581ffc5@linux.dev> (raw)
In-Reply-To: <626477f6-8bda-4cac-8341-c720fd279ba3@infradead.org>
On 6/21/26 2:40 AM, Randy Dunlap wrote:
>
>
> On 6/20/26 5:27 AM, Zenghui Yu wrote:
> > The correct path of the "hotmod" module parameter should be
> > /sys/module/ipmi_si/parameters/hotmod. Fix it.
> >
> > Signed-off-by: Zenghui Yu <zenghui.yu@linux.dev>
> > ---
> > Documentation/driver-api/ipmi.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> There are several other places that use /sys/modules/ instead of
> /sys/module/.
Yup. There are:
Documentation/driver-api/ipmi.rst:This is done using /sys/modules/ipmi_si/parameters/hotmod, which is a
Documentation/process/debugging/kgdb.rst:config string to ``/sys/module/<driver>/parameter/<option>``. The driver
Documentation/translations/zh_CN/admin-guide/mm/damon/lru_sort.rst:参数,或者在 ``/sys/modules/damon_lru_sort/parameters/<parameter>`` 写入正确的
Documentation/translations/zh_CN/admin-guide/mm/damon/lru_sort.rst: # cd /sys/modules/damon_lru_sort/parameters
Documentation/translations/zh_TW/admin-guide/mm/damon/lru_sort.rst:參數,或者在 ``/sys/modules/damon_lru_sort/parameters/<parameter>`` 寫入正確的
Documentation/translations/zh_TW/admin-guide/mm/damon/lru_sort.rst: # cd /sys/modules/damon_lru_sort/parameters
drivers/acpi/sysfs.c: * /sys/modules/acpi/parameters/debug_layer
drivers/acpi/sysfs.c: * /sys/modules/acpi/parameters/debug_level
drivers/acpi/sysfs.c: * /sys/modules/acpi/parameters/trace_method_name
drivers/acpi/sysfs.c: * /sys/modules/acpi/parameters/trace_state
drivers/acpi/sysfs.c: * /sys/modules/acpi/parameters/trace_debug_layer
drivers/acpi/sysfs.c: * /sys/modules/acpi/parameters/trace_debug_level
drivers/acpi/sysfs.c:/* /sys/modules/acpi/parameters/aml_debug_output */
drivers/base/module.c: /* Lookup or create built-in module entry in /sys/modules */
drivers/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c: * On the fly: echo {0,1,2} > /sys/modules/lpvo_usb_gpib/parameters/debug
fs/btrfs/sysfs.c:/* Set perms to 0, disable /sys/module/btrfs/parameter/read_policy interface. */
fs/cachefiles/Kconfig: enabled by setting bits in /sys/modules/cachefiles/parameter/debug or
kernel/params.c:/* sysfs output in /sys/modules/XYZ/parameters/ */
>
> Would you care to fix those also?
I plan to fix them by subsystem like:
https://lore.kernel.org/20260611142518.77343-1-zenghui.yu@linux.dev
Thanks,
Zenghui
next prev parent reply other threads:[~2026-06-20 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 12:27 [PATCH] docs: ipmi: Fix path of the "hotmod" module parameter Zenghui Yu
2026-06-20 15:23 ` Corey Minyard
2026-06-20 18:40 ` Randy Dunlap
2026-06-20 23:06 ` Zenghui Yu [this message]
2026-06-21 0:06 ` Randy Dunlap
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=54430fa8-00ac-47b7-a8e1-b2843581ffc5@linux.dev \
--to=zenghui.yu@linux.dev \
--cc=corbet@lwn.net \
--cc=corey@minyard.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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