From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Woodhouse Subject: Re: [PATCH] BLOCK: Make it possible to disable the block layer Date: Thu, 24 Aug 2006 17:00:16 +0100 Message-ID: <1156435216.3012.130.camel@pmac.infradead.org> References: <32640.1156424442@warthog.cambridge.redhat.com> <20060824152937.GK19810@stusta.de> <1156434274.3012.128.camel@pmac.infradead.org> <20060824155814.GL19810@stusta.de> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: David Howells , Jens Axboe , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:30098 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S1030199AbWHXQAZ (ORCPT ); Thu, 24 Aug 2006 12:00:25 -0400 To: Adrian Bunk In-Reply-To: <20060824155814.GL19810@stusta.de> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 2006-08-24 at 17:58 +0200, Adrian Bunk wrote: > There's no reason for getting linux-kernel swamped with > "my kernel doesn't boot" messages by people who accidentally disabled > this option. By that logic, you should make it necessary to set CONFIG_EMBEDDED before you can set CONFIG_EXT3 != Y or CONFIG_IDE != Y too. However you dress it up, it's pandering to someone who either lacks the wit, or just can't be bothered, to _look_ at what they're doing when they configure their kernel. And it's a bad thing. -- dwmw2