The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Adrian Bunk <bunk@stusta.de>,
	David Woodhouse <dwmw2@infradead.org>,
	David Howells <dhowells@redhat.com>, Jens Axboe <axboe@suse.de>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] BLOCK: Make it possible to disable the block layer
Date: Thu, 24 Aug 2006 20:39:39 +0200	[thread overview]
Message-ID: <44EDF26B.7070404@citd.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0608241838430.16422@yvahk01.tjqt.qr>

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.

Or to quote the GUI-configuration of xine-ui

CONFIG_EXPERIENCE_LEVEL
With the options:
Beginner
Advanced
Expert
Master of the know universe

SCNR. ;-)





Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.


  parent reply	other threads:[~2006-08-24 18:39 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24 13:00 [PATCH] BLOCK: Make it possible to disable the block layer David Howells
2006-08-24 13:13 ` David Woodhouse
2006-08-24 13:34   ` David Howells
2006-08-24 13:40     ` David Woodhouse
2006-08-24 13:54       ` David Howells
2006-08-24 13:47 ` Christoph Hellwig
2006-08-24 14:42 ` Nick Piggin
2006-08-24 15:29 ` Adrian Bunk
2006-08-24 15:44   ` David Woodhouse
2006-08-24 15:58     ` Adrian Bunk
2006-08-24 16:00       ` David Woodhouse
2006-08-24 16:09         ` Adrian Bunk
2006-08-24 16:47           ` Alexey Dobriyan
2006-08-24 17:07             ` Adrian Bunk
2006-08-24 17:16               ` David Woodhouse
2006-08-24 17:34                 ` Randy.Dunlap
2006-08-24 17:48                   ` David Woodhouse
2006-08-24 17:59                     ` Sam Ravnborg
2006-08-25  6:23                       ` Jan Engelhardt
2006-08-25  7:19                         ` Sam Ravnborg
2006-08-24 18:01                     ` Randy.Dunlap
2006-08-25  6:21                 ` Jan Engelhardt
2006-08-25  6:07               ` Jan Engelhardt
2006-08-25 10:37                 ` Adrian Bunk
2006-08-25 13:09                   ` Alexey Dobriyan
2006-08-24 16:39       ` Jan Engelhardt
2006-08-24 16:44         ` David Woodhouse
2006-08-24 16:48         ` Adrian Bunk
2006-08-24 21:31           ` Johannes Stezenbach
2006-08-25  6:04           ` Jan Engelhardt
2006-08-24 18:39         ` Matthias Schniedermeyer [this message]
2006-08-25  6:06           ` Jan Engelhardt
2006-08-24 17:18       ` David Howells
2006-08-24 17:23         ` Adrian Bunk
2006-08-24 16:23 ` Stefan Richter
2006-08-25 12:16 ` Jens Axboe
2006-08-25 13:40   ` David Howells

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44EDF26B.7070404@citd.de \
    --to=ms@citd.de \
    --cc=axboe@suse.de \
    --cc=bunk@stusta.de \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox