From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Kaitao Cheng <kaitao.cheng@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Julian Braha <julianbraha@gmail.com>,
Muchun Song <muchun.song@linux.dev>,
Kaitao Cheng <chengkaitao@kylinos.cn>
Subject: Re: [PATCH] mm/kconfig: Drop redundant dependency wrappers
Date: Tue, 14 Jul 2026 15:28:18 +0200 [thread overview]
Message-ID: <51bc272e-53ae-449c-9ac1-bdac2775e47e@kernel.org> (raw)
In-Reply-To: <20260712093326.8313-1-kaitao.cheng@linux.dev>
On 7/12/26 11:33, Kaitao Cheng wrote:
> From: Kaitao Cheng <chengkaitao@kylinos.cn>
>
> 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.
>
> Suggested-by: Julian Braha <julianbraha@gmail.com>
> Signed-off-by: Kaitao Cheng <chengkaitao@kylinos.cn>
> ---
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
next prev parent reply other threads:[~2026-07-14 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 9:33 [PATCH] mm/kconfig: Drop redundant dependency wrappers Kaitao Cheng
2026-07-14 13:28 ` David Hildenbrand (Arm) [this message]
2026-07-14 14:24 ` Lorenzo Stoakes (ARM)
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=51bc272e-53ae-449c-9ac1-bdac2775e47e@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chengkaitao@kylinos.cn \
--cc=julianbraha@gmail.com \
--cc=kaitao.cheng@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox