From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Adrian Bunk <bunk@stusta.de>
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 17:41:28 +0000 [thread overview]
Message-ID: <20060106174127.GE16093@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060106173547.GR12131@stusta.de>
On Fri, Jan 06, 2006 at 06:35:47PM +0100, Adrian Bunk 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.
NACK. MTD_OBSOLETE_CHIPS still hasn't been fixed and must be fixed
_before_ this patch can go in.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-01-06 17:41 UTC|newest]
Thread overview: 39+ 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 [this message]
2006-01-06 17:54 ` Adrian Bunk
2006-01-06 17:49 ` Jesper Juhl
2006-01-06 18:06 ` Adrian Bunk
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:05 ` Adrian Bunk
2005-12-13 18:05 ` Adrian Bunk
2005-12-13 18:28 ` Geert Uytterhoeven
2005-12-13 18:28 ` Geert Uytterhoeven
2005-12-13 18:28 ` Geert Uytterhoeven
2005-12-13 18:28 ` Geert Uytterhoeven
2005-12-13 18:51 ` Adrian Bunk
2005-12-13 18:51 ` Adrian Bunk
2005-12-13 18:51 ` Adrian Bunk
2005-12-13 18:51 ` Adrian Bunk
2005-12-13 18:59 ` Jesper Juhl
2005-12-13 18:59 ` Jesper Juhl
2005-12-13 18:59 ` Jesper Juhl
2005-12-13 18:59 ` Jesper Juhl
2005-12-13 20:01 ` Russell King
2005-12-13 20:01 ` Russell King
2005-12-13 20:01 ` Russell King
2005-12-13 20:19 ` Adrian Bunk
2005-12-13 20:19 ` Adrian Bunk
2005-12-13 20:19 ` Adrian Bunk
2005-12-13 22:01 ` Russell King
2005-12-13 22:01 ` Russell King
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=20060106174127.GE16093@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--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 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.