From: Borislav Petkov <bp@alien8.de>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, "David S. Miller" <davem@davemloft.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs/Kconfig: Enable HUGETLBFS only if ARCH_SUPPORTS_HUGETLBFS
Date: Mon, 14 Jul 2025 11:49:09 +0200 [thread overview]
Message-ID: <20250714094909.GBaHTSlW8nkuINON9p@fat_crate.local> (raw)
In-Reply-To: <f86c9ec6-d82d-4d0c-80b2-504f7c6da22e@arm.com>
On Mon, Jul 14, 2025 at 08:05:31AM +0530, Anshuman Khandual wrote:
> The original first commit had added 'BROKEN', although currently there
> are no explanations about it in the tree.
commit c0dde7404aff064bff46ae1d5f1584d38e30c3bf
Author: Linus Torvalds <torvalds@home.osdl.org>
Date: Sun Aug 17 21:23:57 2003 -0700
Add CONFIG_BROKEN (default 'n') to hide known-broken drivers.
diff --git a/init/Kconfig b/init/Kconfig
index 0d1629e23398..5c012aeb2a8f 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -32,6 +32,17 @@ config EXPERIMENTAL
you say Y here, you will be offered the choice of using features or
drivers that are currently considered to be in the alpha-test phase.
+config BROKEN
+ bool "Prompt for old and known-broken drivers"
+ depends on EXPERIMENTAL
+ default n
+ help
+ This option allows you to choose whether you want to try to
+ compile (and fix) old drivers that haven't been updated to
+ new infrastructure.
+
+ If unsure, say N.
+
endmenu
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2025-07-14 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 10:29 Anshuman Khandual
2025-07-12 23:15 ` Andrew Morton
2025-07-14 2:35 ` Anshuman Khandual
2025-07-14 9:49 ` Borislav Petkov [this message]
2025-07-15 0:31 ` Andrew Morton
2025-07-29 15:50 ` Christophe Leroy
2025-07-29 15:52 ` Christophe Leroy
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=20250714094909.GBaHTSlW8nkuINON9p@fat_crate.local \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=davem@davemloft.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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