From: Corey Minyard <corey@minyard.net>
To: Zenghui Yu <zenghui.yu@linux.dev>
Cc: openipmi-developer@lists.sourceforge.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org
Subject: Re: [PATCH] docs: ipmi: Fix path of the "hotmod" module parameter
Date: Sat, 20 Jun 2026 10:23:42 -0500 [thread overview]
Message-ID: <ajawfhU5nCR93DL_@mail.minyard.net> (raw)
In-Reply-To: <20260620122747.7902-1-zenghui.yu@linux.dev>
On Sat, Jun 20, 2026 at 08:27:47PM +0800, Zenghui Yu wrote:
> The correct path of the "hotmod" module parameter should be
> /sys/module/ipmi_si/parameters/hotmod. Fix it.
Thanks, it's in my queue.
-corey
>
> Signed-off-by: Zenghui Yu <zenghui.yu@linux.dev>
> ---
> Documentation/driver-api/ipmi.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/driver-api/ipmi.rst b/Documentation/driver-api/ipmi.rst
> index f52ab2df2569..d08cee98e34a 100644
> --- a/Documentation/driver-api/ipmi.rst
> +++ b/Documentation/driver-api/ipmi.rst
> @@ -495,7 +495,7 @@ tuned to the user's desired performance.
>
> The driver supports a hot add and remove of interfaces. This way,
> interfaces can be added or removed after the kernel is up and running.
> -This is done using /sys/modules/ipmi_si/parameters/hotmod, which is a
> +This is done using /sys/module/ipmi_si/parameters/hotmod, which is a
> write-only parameter. You write a string to this interface. The string
> has the format::
>
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-06-20 15:23 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 [this message]
2026-06-20 18:40 ` Randy Dunlap
2026-06-20 23:06 ` Zenghui Yu
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=ajawfhU5nCR93DL_@mail.minyard.net \
--to=corey@minyard.net \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=skhan@linuxfoundation.org \
--cc=zenghui.yu@linux.dev \
/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