All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@linuxtv.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.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 23:31:14 +0200	[thread overview]
Message-ID: <20060824213114.GA18667@linuxtv.org> (raw)
In-Reply-To: <20060824164808.GN19810@stusta.de>

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

  reply	other threads:[~2006-08-24 21:32 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 [this message]
2006-08-25  6:04           ` Jan Engelhardt
2006-08-24 18:39         ` Matthias Schniedermeyer
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=20060824213114.GA18667@linuxtv.org \
    --to=js@linuxtv.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.