[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060824213114.GA18667@linuxtv.org>
Date: Thu, 24 Aug 2006 23:31:14 +0200
From: Johannes Stezenbach <js@...uxtv.org>
To: Adrian Bunk <bunk@...sta.de>
Cc: Jan Engelhardt <jengelh@...ux01.gwdg.de>,
David Woodhouse <dwmw2@...radead.org>,
David Howells <dhowells@...hat.com>,
Jens Axboe <axboe@...e.de>, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] BLOCK: Make it possible to disable the block layer
On Thu, Aug 24, 2006, Adrian Bunk wrote:
> On Thu, Aug 24, 2006 at 06:39:14PM +0200, Jan Engelhardt wrote:
> > >> On Thu, 2006-08-24 at 17:29 +0200, Adrian Bunk wrote:
> > >> > bool "Enable the block layer" depends on EMBEDDED
> > >>
> > >> Please. no. CONFIG_EMBEDDED was a bad idea in the first place -- its
> > >> sole purpose is to pander to Aunt Tillie.
> > >
> > >It's not for Aunt Tillie.
> > >It's for an average system administrator who compiles his own kernel.
> > >
> > >CONFIG_BLOCK=n will only be for the "the kernel must become as fast as
> > >possible, and I really know what I'm doing" people.
> >
> > Then that should be CONFIG_I_AM_AN_EXPERT (CONFIG_EXPERT), not
> > CONFIG_EMBEDDED.
>
> It makes sense that there is one option only for additional space
> savings.
>
> But you are right, we need a second option for not space related expert
> options.
I think the sole purpose of CONFIG_EMBEDDED is to reduce noise from
silly pseudo-bug reports. The rather uninteresting name helps.
If you have CONFIG_EXPERT, of course _everone_ will enable it,
shoot themselves in the foot and will be happy to inform you
about it, wasting their and _your_ time.
Johannes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists