Re: [2.6 patch] don't allow users to set CONFIG_BROKEN=y

[Randy.Dunlap]

On Fri, 6 Jan 2006, Jesper Juhl wrote:

> On 1/6/06, Adrian Bunk <bunk@xxxxxxxxx> wrote:
> > On Fri, Jan 06, 2006 at 06:49:55PM +0100, Jesper Juhl wrote:
> > > On 1/6/06, Adrian Bunk <bunk@xxxxxxxxx> 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?
> >
> Hmm, when I'm looking for broken stuff to fix ;)
> I guess you are right, ordinary users don't need it.. Ok, count me in
> as supporting this move.

I'm having a little trouble determining why it matters.

Are you trying to cut down on lkml bug reports or just make
it harder on everyone?

-- 
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/