From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,rppt@kernel.org,henry.elderman.edu+linux@gmail.com,henry.elderman.edu@gmail.com,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-execmem-fix-fallback_end-description-in-kernel-doc.patch removed from -mm tree
Date: Mon, 24 Aug 2026 18:54:20 -0700 [thread overview]
Message-ID: <20260825015420.8CD2B1F000E9@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/execmem: fix fallback_end description in kernel-doc
has been removed from the -mm tree. Its filename was
mm-execmem-fix-fallback_end-description-in-kernel-doc.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: Henry Elderman <henry.elderman.edu@gmail.com>
Subject: mm/execmem: fix fallback_end description in kernel-doc
Date: Fri, 7 Aug 2026 11:19:58 +0200
The kernel-doc for struct execmem_range incorrectly describes @fallback_end
as "start". Correct it to "end".
Link: https://lore.kernel.org/20260807091958.4735-1-henry.elderman.edu+linux@gmail.com
Signed-off-by: Henry Elderman <henry.elderman.edu+linux@gmail.com>
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/execmem.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/include/linux/execmem.h~mm-execmem-fix-fallback_end-description-in-kernel-doc
+++ a/include/linux/execmem.h
@@ -89,7 +89,7 @@ static inline int execmem_restore_rox(vo
* @end: address space end (inclusive)
* @fallback_start: start of the secondary address space range for fallback
* allocations on architectures that require it
- * @fallback_end: start of the secondary address space (inclusive)
+ * @fallback_end: end of the secondary address space (inclusive)
* @pgprot: permissions for memory in this address space
* @alignment: alignment required for text allocations
* @flags: options for memory allocations for this range
_
Patches currently in -mm which might be from henry.elderman.edu@gmail.com are
reply other threads:[~2026-08-25 1:54 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=20260825015420.8CD2B1F000E9@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=henry.elderman.edu+linux@gmail.com \
--cc=henry.elderman.edu@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.