From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,rppt@kernel.org,kmehltretter@gmail.com,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-secretmem-fix-the-enable-parameter-description.patch removed from -mm tree
Date: Mon, 12 Oct 2026 21:32:03 -0700 [thread overview]
Message-ID: <20261013043204.077BD1F000FF@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/secretmem: fix the enable parameter description
has been removed from the -mm tree. Its filename was
mm-secretmem-fix-the-enable-parameter-description.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Karl Mehltretter <kmehltretter@gmail.com>
Subject: mm/secretmem: fix the enable parameter description
Date: Sat, 12 Sep 2026 13:48:59 +0200
The module parameter is enable, but its MODULE_PARM_DESC() names the
variable behind it, secretmem_enable. secretmem is built in, so the
description only reaches modules.builtin.modinfo, where it is filed under
secretmem_enable while the parmtype line and
/sys/module/secretmem/parameters/ say enable.
Use the parameter name in the description.
Link: https://lore.kernel.org/20260912114859.88957-1-kmehltretter@gmail.com
Fixes: 1507f51255c9 ("mm: introduce memfd_secret system call to create "secret" memory areas")
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Assisted-by: LLM
---
mm/secretmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/secretmem.c~mm-secretmem-fix-the-enable-parameter-description
+++ a/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;
_
Patches currently in -mm which might be from kmehltretter@gmail.com are
mm-damon-core-preserve-the-quota-passed-to-damon_new_scheme.patch
mm-damon-tests-core-kunit-test-preservation-of-quota-state.patch
mm-damon-tests-core-kunit-test-psi-goal-values-with-explicit-samples.patch
squashfs-fix-fragment-index-table-sizing-overflow-on-32-bit.patch
squashfs-make-the-fragment-index-table-bounds-check-overflow-safe.patch
reply other threads:[~2026-10-13 4:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261013043204.077BD1F000FF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=kmehltretter@gmail.com \
--cc=mm-commits@vger.kernel.org \
--cc=rppt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.