From: Julian Braha <julianbraha@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Thomas Gleixner" <tglx@kernel.org>, "Rong Xu" <xur@google.com>,
"Kees Cook" <kees@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Ruan Jinjie" <ruanjinjie@huawei.com>,
gourry@gourry.net, "Lukas Bulwahn" <lukas.bulwahn@redhat.com>,
"Ryan Roberts" <ryan.roberts@arm.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/Kconfig: fix dead conditions by removing dead options
Date: Fri, 21 Aug 2026 11:13:16 +0100 [thread overview]
Message-ID: <c0e8d7c8-339f-4f82-a4a8-49b67d120705@gmail.com> (raw)
In-Reply-To: <880b651b-a032-48f8-96ef-03a37b3ad50c@app.fastmail.com>
On 7/31/26 11:41, Arnd Bergmann wrote:
> On Wed, Jul 29, 2026, at 23:05, Julian Braha wrote:
>> These two 'int' options:
>>
>> ARCH_MMAP_RND_BITS_DEFAULT
>> ARCH_MMAP_RND_COMPAT_BITS_DEFAULT
>>
>> are used directly as conditions for defaults. 'int' options should not be
>> used as conditions, because they will always evaluate to false.
>>
>> Let's remove these options, because they are not used anywhere else.
>>
>> This dead code was found by kconfirm, a static analysis tool for Kconfig.
>>
>> Signed-off-by: Julian Braha <julianbraha@gmail.com>
> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Sorry to bother, but whose tree would this patch go into?
I'd like to add some type checking into Kconfig, but I need to wait
until this patch is merged before making this a hard error.
- Julian Braha
next prev parent reply other threads:[~2026-08-21 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 21:05 [PATCH] arch/Kconfig: fix dead conditions by removing dead options Julian Braha
2026-07-31 10:41 ` Arnd Bergmann
2026-08-21 10:13 ` Julian Braha [this message]
2026-08-03 3:50 ` Jinjie Ruan
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=c0e8d7c8-339f-4f82-a4a8-49b67d120705@gmail.com \
--to=julianbraha@gmail.com \
--cc=arnd@arndb.de \
--cc=gourry@gourry.net \
--cc=jani.nikula@linux.intel.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=peterz@infradead.org \
--cc=ruanjinjie@huawei.com \
--cc=ryan.roberts@arm.com \
--cc=tglx@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=xur@google.com \
/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.