[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060901014702.GZ18276@stusta.de>
Date: Fri, 1 Sep 2006 03:47:02 +0200
From: Adrian Bunk <bunk@...sta.de>
To: David Woodhouse <dwmw2@...radead.org>
Cc: "Randy.Dunlap" <rdunlap@...otime.net>,
Roman Zippel <zippel@...ux-m68k.org>,
Stefan Richter <stefanr@...6.in-berlin.de>,
linux-kernel@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>,
David Howells <dhowells@...hat.com>,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
On Thu, Aug 31, 2006 at 06:27:27PM -0700, David Woodhouse wrote:
> On Thu, 2006-08-31 at 17:48 -0700, Randy.Dunlap wrote:
> > But David, you edit .config anyway, so who is "make *config" for?
> > Not that I want enable Tillie very much..
>
> I edit .config but still have to use 'make oldconfig' afterwards. And it
> screws me over because of all this 'select' nonsense. This used to
> work...
> sed -i /^CONFIG_SCSI=/d .config
> yes n | make oldconfig
>
> So "make *config" certainly isn't optimised for me, although of course I
> do have to use it. It seems to be increasingly optimised for Aunt
> Tillie.
The vast majority of konfig user who might have a master in computer
science (like our Aunt Tillie has) but aren't kernel hackers have
different needs from kernel hackers.
I know how hard it is to e.g. find a maximum .config with FW_LOADER=n.
Normal kconfig users and kernel hackers have different needs, and the
real solution fitting the needs of both groups would in this case be
a patch to kconfig that allows a kernel hacker to specify which option
to deselect and does the rest automatically.
> dwmw2
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
-
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