From: Randy Dunlap <rdunlap@infradead.org>
To: Zenghui Yu <zenghui.yu@linux.dev>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: mcgrof@kernel.org, petr.pavlu@suse.com, da.gomez@kernel.org,
samitolvanen@google.com, atomlin@atomlin.com
Subject: Re: [PATCH] params: fix path of /sys/module/XYZ/parameters/ in comment
Date: Sun, 21 Jun 2026 12:44:43 -0700 [thread overview]
Message-ID: <9069a13d-bed2-4e1b-9675-4c6bfe42e4f2@infradead.org> (raw)
In-Reply-To: <20260621082223.11439-1-zenghui.yu@linux.dev>
On 6/21/26 1:22 AM, Zenghui Yu wrote:
> The comment wrongly references to /sys/modules/XYZ/parameters/ directory
> instead of /sys/module/XYZ/parameters/. Fix it.
>
> Signed-off-by: Zenghui Yu <zenghui.yu@linux.dev>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
>
> kernel/params.c is not covered by any MAINTAINERS entry. I assume it should
> be a "MODULE SUPPORT" stuff?
>
> kernel/params.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/params.c b/kernel/params.c
> index a668863a4bb6..3456b104efc9 100644
> --- a/kernel/params.c
> +++ b/kernel/params.c
> @@ -538,7 +538,7 @@ const struct kernel_param_ops param_ops_string = {
> };
> EXPORT_SYMBOL(param_ops_string);
>
> -/* sysfs output in /sys/modules/XYZ/parameters/ */
> +/* sysfs output in /sys/module/XYZ/parameters/ */
> #define to_module_attr(n) container_of_const(n, struct module_attribute, attr)
> #define to_module_kobject(n) container_of(n, struct module_kobject, kobj)
>
--
~Randy
next prev parent reply other threads:[~2026-06-21 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-21 8:22 [PATCH] params: fix path of /sys/module/XYZ/parameters/ in comment Zenghui Yu
2026-06-21 19:44 ` Randy Dunlap [this message]
2026-06-21 21:33 ` Aaron Tomlin
2026-07-09 8:16 ` Petr Pavlu
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=9069a13d-bed2-4e1b-9675-4c6bfe42e4f2@infradead.org \
--to=rdunlap@infradead.org \
--cc=atomlin@atomlin.com \
--cc=da.gomez@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--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