From: David Woodhouse <dwmw2@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: 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 14:13:13 +0100 [thread overview]
Message-ID: <1156425193.3012.32.camel@pmac.infradead.org> (raw)
In-Reply-To: <32640.1156424442@warthog.cambridge.redhat.com>
On Thu, 2006-08-24 at 14:00 +0100, David Howells wrote:
> Make it possible to disable the block layer. Not all embedded devices require
> it, some can make do with just JFFS2, NFS, ramfs, etc - none of which require
> the block layer to be present.
>
> This patch does the following:
>
> (*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev
> support.
Excellent -- I've been meaning to do this (and occasionally hacking on
it half-heartedly before getting distracted by something else shiny) for
a _long_ time.
It looks good in general.
> (*) The contents of a number of filesystem- and blockdev-specific header files
> are now contingent on their own configuration options. This includes:
> Ext3/JBD, RAID, MSDOS and ReiserFS.
Why? Those header files shouldn't be included from anywhere _but_ the
code in question, and in fact should probably be just moved into fs/foo
instead of living in include/linux/foo_fs.h.
And please, _never_ make anything dependent on CONFIG_foo_MODULE.
--
dwmw2
next prev parent reply other threads:[~2006-08-24 13:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 13:00 David Howells
2006-08-24 13:13 ` David Woodhouse [this message]
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
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=1156425193.3012.32.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=axboe@suse.de \
--cc=dhowells@redhat.com \
--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
all inboxes | Powered by JetHome®