From: Mike Rapoport <rppt@kernel.org>
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Subject: Re: [PATCH] mm/secretmem: Fix the enable parameter description
Date: Sun, 6 Sep 2026 22:04:58 +0300 [thread overview]
Message-ID: <ap25Wj-kt2nsMn59@kernel.org> (raw)
In-Reply-To: <20260906171523.3009-1-kmehltretter@gmail.com>
On Sun, Sep 06, 2026 at 07:15:23PM +0200, Karl Mehltretter wrote:
> The module parameter is enable, but its MODULE_PARM_DESC() names the
> variable behind it, secretmem_enable, so modinfo describes a parameter
> that does not exist and shows no description for the real one.
Hmm, does modinfo show secretmem description at all?
> Use the parameter name in the description.
>
> Fixes: 1507f51255c9 ("mm: introduce memfd_secret system call to create "secret" memory areas")
> Assisted-by: LLM
Please use the form described in
https://docs.kernel.org/process/coding-assistants.html#attribution
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> mm/secretmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/secretmem.c b/mm/secretmem.c
> index 384f5cfc457f..4e32bf55a599 100644
> --- a/mm/secretmem.c
> +++ b/mm/secretmem.c
> @@ -39,7 +39,7 @@
>
> static bool secretmem_enable __ro_after_init = 1;
> module_param_named(enable, secretmem_enable, bool, 0400);
> -MODULE_PARM_DESC(secretmem_enable,
> +MODULE_PARM_DESC(enable,
> "Enable secretmem and memfd_secret(2) system call");
>
> static atomic_t secretmem_users;
>
> base-commit: 986c24e0fe44f844b44d365b71ce831947f50298
> --
> 2.53.0
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-09-06 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 17:15 [PATCH] mm/secretmem: Fix the enable parameter description Karl Mehltretter
2026-09-06 19:04 ` Mike Rapoport [this message]
2026-09-07 20:55 ` Karl Mehltretter
2026-09-12 11:48 ` [PATCH v2] " Karl Mehltretter
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=ap25Wj-kt2nsMn59@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kmehltretter@gmail.com \
--cc=linux-mm@kvack.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