From: dimitri.gorokhovik@free.fr
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, jean-paul.saman@nxp.com
Subject: [PATCH] initramfs should not depend on CONFIG_BLOCK
Date: Mon, 05 Mar 2007 23:09:34 +0100 [thread overview]
Message-ID: <1173132574.45ec951e4c014@imp.free.fr> (raw)
initramfs ended up depending on BLOCK:
INITRAMFS_SOURCE <-- BLK_DEV_INITRD <-- BLOCK
This inhibits use of customized-initramfs-over-ramfs without block layer
(ramfs would still be enabled), useful in embedded applications.
Move BLK_DEV_INITRD out of 'drivers/block/Kconfig' and into 'init/Kconfig',
make it unconditional.
Signed-off-by: Dimitri Gorokhovik <dimitri.gorokhovik@free.fr>
--- linux-2.6.21-rc2-git4-broken/init/Kconfig 2007-03-05 23:20:27.000000000 +0100
+++ linux-2.6.21-rc2-git4-fixed/init/Kconfig 2007-03-05 22:22:48.000000000 +0100
@@ -304,6 +304,23 @@ config RELAY
If unsure, say N.
+config BLK_DEV_INITRD
+ bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
+ depends on BROKEN || !FRV
+ help
+ The initial RAM filesystem is a ramfs which is loaded by the
+ boot loader (loadlin or lilo) and that is mounted as root
+ before the normal boot procedure. It is typically used to
+ load modules needed to mount the "real" root file system,
+ etc. See <file:Documentation/initrd.txt> for details.
+
+ If RAM disk support (BLK_DEV_RAM) is also included, this
+ also enables initial RAM disk (initrd) support and adds
+ 15 Kbytes (more on some other architectures) to the kernel size.
+
+ If unsure say Y.
+
if BLK_DEV_INITRD
source "usr/Kconfig"
--- linux-2.6.21-rc2-git4-broken/drivers/block/Kconfig 2007-03-05 23:20:21.000000000 +0100
+++ linux-2.6.21-rc2-git4-fixed/drivers/block/Kconfig 2007-03-05 22:22:48.000000000 +0100
@@ -406,21 +406,6 @@ config BLK_DEV_RAM_BLOCKSIZE
setups function - apparently needed by the rd_load_image routine
that supposes the filesystem in the image uses a 1024 blocksize.
-config BLK_DEV_INITRD
- bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
- depends on BROKEN || !FRV
- help
- The initial RAM filesystem is a ramfs which is loaded by the
- boot loader (loadlin or lilo) and that is mounted as root
- before the normal boot procedure. It is typically used to
- load modules needed to mount the "real" root file system,
- etc. See <file:Documentation/initrd.txt> for details.
-
- If RAM disk support (BLK_DEV_RAM) is also included, this
- also enables initial RAM disk (initrd) support and adds
- 15 Kbytes (more on some other architectures) to the kernel size.
-
- If unsure say Y.
config CDROM_PKTCDVD
tristate "Packet writing on CD/DVD media"
@@ -472,3 +457,5 @@ config ATA_OVER_ETH
endmenu
endif
reply other threads:[~2007-03-05 22:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1173132574.45ec951e4c014@imp.free.fr \
--to=dimitri.gorokhovik@free.fr \
--cc=akpm@linux-foundation.org \
--cc=jean-paul.saman@nxp.com \
--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
Powered by JetHome