Subject: Re: [PATCH] BLOCK: Make it possible to disable the block layer
From: David Woodhouse <dwmw2@infradead.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: David Howells <dhowells@redhat.com>, Jens Axboe <axboe@suse.de>,
       linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <20060824155814.GL19810@stusta.de>
References: <32640.1156424442@warthog.cambridge.redhat.com>
	 <20060824152937.GK19810@stusta.de>
	 <1156434274.3012.128.camel@pmac.infradead.org>
	 <20060824155814.GL19810@stusta.de>
Content-Type: text/plain
Date: Thu, 24 Aug 2006 17:00:16 +0100
Message-Id: <1156435216.3012.130.camel@pmac.infradead.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 777
Lines: 20

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

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