From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,tj@kernel.org,surenb@google.com,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [alternative-merged] lib-kconfigdebug-make-debug_force_weak_per_cpu-depend-on-s390alpha.patch removed from -mm tree
Date: Wed, 12 Aug 2026 14:26:55 -0700 [thread overview]
Message-ID: <20260812212656.37C0D1F000E9@smtp.kernel.org> (raw)
The quilt patch titled
Subject: lib/Kconfig.debug: make DEBUG_FORCE_WEAK_PER_CPU depend on S390||ALPHA
has been removed from the -mm tree. Its filename was
lib-kconfigdebug-make-debug_force_weak_per_cpu-depend-on-s390alpha.patch
This patch was dropped because an alternative patch was or shall be merged
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: lib/Kconfig.debug: make DEBUG_FORCE_WEAK_PER_CPU depend on S390||ALPHA
Date: Mon Aug 10 08:50:56 PM PDT 2026
CONFIG_DEBUG_FORCE_WEAK_PER_CPU appears to be alpha-specific. The Kconfig
help text says s390 can need it also, but the comment in percpu-defs.h
only mentions alpha. The original commit 7c756e6e19e7 ("percpu: implement
optional weak percpu definitions") mentions both alpha and s390.
All quite mysterious and perhaps this feature is no longer needed.
However x86_64 allmodconfig enables it, and because mm/alloc_tag.c
requires !DEBUG_FORCE_WEAK_PER_CPU (another mystery), alloc_tag isn't
getting allmodconfig build coverage.
Adding `depends on S390||ALPHA' fixes this.
Cc: Tejun Heo <tj@kernel.org>
Cc: Suren Baghdasaryan <surenb@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/Kconfig.debug | 1 +
1 file changed, 1 insertion(+)
--- a/lib/Kconfig.debug~lib-kconfigdebug-make-debug_force_weak_per_cpu-depend-on-s390alpha
+++ a/lib/Kconfig.debug
@@ -616,6 +616,7 @@ config BUILTIN_MODULE_RANGES
config DEBUG_FORCE_WEAK_PER_CPU
bool "Force weak per-cpu definitions"
depends on DEBUG_KERNEL
+ depends on S390 || ALPHA
help
s390 and alpha require percpu variables in modules to be
defined weak to work around addressing range issue which
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
selftests-cgroup-test_zswap-skip-test_no_kmem_bypass-if-debugfs-is-unavailable-fix.patch
mm-hmmc-hmm_do_fault-suppress-sparse-warning.patch
mm-hmmc-hmm_do_fault-suppress-sparse-warning-fix.patch
drivers-media-v4l2-core-v4l2-vp9c-reduce-inlining.patch
reply other threads:[~2026-08-12 21:26 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=20260812212656.37C0D1F000E9@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=mm-commits@vger.kernel.org \
--cc=surenb@google.com \
--cc=tj@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.