From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,vbabka@kernel.org,surenb@google.com,rppt@kernel.org,muchun.song@linux.dev,mhocko@suse.com,ljs@kernel.org,liam@infradead.org,julianbraha@gmail.com,david@kernel.org,chengkaitao@kylinos.cn,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-kconfig-drop-redundant-dependency-wrappers.patch removed from -mm tree
Date: Mon, 24 Aug 2026 18:44:21 -0700 [thread overview]
Message-ID: <20260825014422.1CD601F00A3A@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/kconfig: drop redundant dependency wrappers
has been removed from the -mm tree. Its filename was
mm-kconfig-drop-redundant-dependency-wrappers.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: Kaitao Cheng <chengkaitao@kylinos.cn>
Subject: mm/kconfig: drop redundant dependency wrappers
Date: Sun, 12 Jul 2026 17:33:26 +0800
Some mm Kconfig entries repeat dependencies that are already expressed by
their surrounding blocks or menus.
The zsmalloc allocator options menu already depends on ZSMALLOC, so the
outer if ZSMALLOC block does not add any extra constraint.
MEMORY_HOTREMOVE and MHP_MEMMAP_ON_MEMORY are both inside the if
MEMORY_HOTPLUG block, so their local depends on MEMORY_HOTPLUG entries are
redundant.
PTE_MARKER_UFFD_WP is the only entry under if USERFAULTFD. Move the
USERFAULTFD dependency into the symbol itself and combine it with the
architecture support dependency.
This keeps the same visibility and defaults while avoiding duplicate
dependency expressions.
Link: https://lore.kernel.org/20260712093326.8313-1-kaitao.cheng@linux.dev
Signed-off-by: Kaitao Cheng <chengkaitao@kylinos.cn>
Suggested-by: Julian Braha <julianbraha@gmail.com>
Reviewed-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
Cc: Liam R. Howlett <liam@infradead.org>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Mike Rapoport <rppt@kernel.org>
Cc: Muchun Song <muchun.song@linux.dev>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Vlastimil Babka <vbabka@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/Kconfig | 10 +---------
1 file changed, 1 insertion(+), 9 deletions(-)
--- a/mm/Kconfig~mm-kconfig-drop-redundant-dependency-wrappers
+++ a/mm/Kconfig
@@ -125,8 +125,6 @@ config ZSWAP_COMPRESSOR_DEFAULT
config ZSMALLOC
tristate
-if ZSMALLOC
-
menu "Zsmalloc allocator options"
depends on ZSMALLOC
@@ -161,8 +159,6 @@ config ZSMALLOC_CHAIN_SIZE
endmenu
-endif
-
menu "Slab allocator options"
config SLUB
@@ -583,12 +579,10 @@ endchoice
config MEMORY_HOTREMOVE
bool "Allow for memory hot remove"
- depends on MEMORY_HOTPLUG
select MIGRATION
config MHP_MEMMAP_ON_MEMORY
def_bool y
- depends on MEMORY_HOTPLUG
depends on ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE
endif # MEMORY_HOTPLUG
@@ -1393,17 +1387,15 @@ menuconfig USERFAULTFD
Enable the userfaultfd() system call that allows to intercept and
handle page faults in userland.
-if USERFAULTFD
config PTE_MARKER_UFFD_WP
bool "Userfaultfd write protection support for shmem/hugetlbfs"
default y
- depends on HAVE_ARCH_USERFAULTFD_WP
+ depends on USERFAULTFD && HAVE_ARCH_USERFAULTFD_WP
help
Allows to create marker PTEs for userfaultfd write protection
purposes. It is required to enable userfaultfd write protection on
file-backed memory types like shmem and hugetlbfs.
-endif # USERFAULTFD
# multi-gen LRU {
config LRU_GEN
_
Patches currently in -mm which might be from chengkaitao@kylinos.cn are
reply other threads:[~2026-08-25 1:44 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=20260825014422.1CD601F00A3A@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=chengkaitao@kylinos.cn \
--cc=david@kernel.org \
--cc=julianbraha@gmail.com \
--cc=liam@infradead.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=muchun.song@linux.dev \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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.