From: Adrian Bunk <bunk@stusta.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] don't allow users to set CONFIG_BROKEN=y
Date: Fri, 6 Jan 2006 19:06:26 +0100 [thread overview]
Message-ID: <20060106180626.GV12131@stusta.de> (raw)
In-Reply-To: <9a8748490601060949g4765a4dcrfab4adab4224b5ad@mail.gmail.com>
On Fri, Jan 06, 2006 at 06:49:55PM +0100, Jesper Juhl wrote:
> On 1/6/06, Adrian Bunk <bunk@stusta.de> wrote:
> > Do not allow people to create configurations with CONFIG_BROKEN=y.
> >
> > The sole reason for CONFIG_BROKEN=y would be if you are working on
> > fixing a broken driver, but in this case editing the Kconfig file is
> > trivial.
> >
> > Never ever should a user enable CONFIG_BROKEN.
> >
> I disagree (slightly) with this patch for a few reasons:
>
> - It's very convenient to be able to enable it through menuconfig.
And when do you really need it?
> - Being able to easily enable it in menuconfig, then browse through
> the menus to look for something matching your hardware is nice, even
> if that something is marked BROKEN at least you've then found a place
> to start working on. A lot simpler than digging through directories.
Our menus are mostly made for _users_.
The more common are users accidentially enabling CONFIG_BROKEN and then
wondering why a driver isn't compiling or working.
And in my experience, when searching whether hardware might be supported
a grep through the kernel sources brings you more than reading often
outdated Kconfig help texts. Besides this, a BROKEN driver usually has
the same value for the user as a non-existing driver.
> - Some things marked BROKEN may not be 100% broken and may actually
> work for some specific things, so if you know that it works for your
> use, then being able to easily enable BROKEN and then whatever it is
> you need is nice.
In reality, people accidentially turn on CONFIG_BROKEN, enable a broken
driver, and wonder why it isn't working as expected.
If you know the driver is marked as BROKEN and if you want to use it
despite this, editing the Kconfig file is trivial.
Unless you _really_ know what you are doing, no driver for your hard
disk is better than a broken driver.
> Perhaps just move it below the Kernel Hacking menu instead, users
> don't go there (or if they do they damn well should know what they are
> doing).
>...
Enabling MAGIC_SYSRQ for being able to sync the disks for crashed
machines...
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-01-06 18:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 17:35 [2.6 patch] don't allow users to set CONFIG_BROKEN=y Adrian Bunk
2006-01-06 17:41 ` Russell King
2006-01-06 17:54 ` Adrian Bunk
2006-01-06 17:49 ` Jesper Juhl
2006-01-06 18:06 ` Adrian Bunk [this message]
2006-01-06 18:26 ` Jesper Juhl
2006-01-06 18:39 ` Randy.Dunlap
2006-01-06 18:58 ` Adrian Bunk
2006-01-06 19:14 ` Jan Engelhardt
2006-01-06 21:11 ` David Lang
2006-01-06 22:37 ` Adrian Bunk
2006-01-06 22:39 ` David Lang
2006-01-06 22:53 ` Adrian Bunk
2006-01-06 22:25 ` Daniel Barkalow
-- strict thread matches above, loose matches on Subject: below --
2006-01-19 1:40 Adrian Bunk
2005-12-11 18:52 [2.6 patch] defconfig's shouldn't " Adrian Bunk
2005-12-11 19:21 ` Russell King
2005-12-11 19:31 ` Adrian Bunk
2005-12-11 19:44 ` Russell King
2005-12-13 0:10 ` Adrian Bunk
2005-12-13 13:34 ` Simon Richter
2005-12-13 14:00 ` Adrian Bunk
2005-12-13 17:31 ` Russell King
2005-12-13 18:05 ` [2.6 patch] don't allow users to " Adrian Bunk
2005-12-13 18:28 ` Geert Uytterhoeven
2005-12-13 18:51 ` Adrian Bunk
2005-12-13 18:59 ` Jesper Juhl
2005-12-13 20:01 ` Russell King
2005-12-13 20:19 ` Adrian Bunk
2005-12-13 22:01 ` Russell King
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=20060106180626.GV12131@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.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