In arch/arm/kernel/setup.c:setup_ramdisk(), rd_size is set from the
boot tags. The replacement ramdisk driver has rd_size as static
which causes linking to fail when ramdisk is built-in.
Signed-off-by: Byron Bradley <[EMAIL PROTECTED]>
Cc: Nick Piggin <[EMAIL PROTECTED]>
Cc: Russell King <[EMAIL PROTECTED]>
---
This patch applies against 2.6.24-rc8-mm1 and has not been tested,
it is only know to compile. I'm not sure if there is a better way
to set rd_size or if this is OK.
drivers/block/brd.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/block/brd.c b/drivers/block/brd.c
index 5ef1d26..8536480 100644
--- a/drivers/block/brd.c
+++ b/drivers/block/brd.c
@@ -385,7 +385,7 @@ static struct block_device_operations brd_fops = {
* And now the modules code and kernel interface.
*/
static int rd_nr;
-static int rd_size = CONFIG_BLK_DEV_RAM_SIZE;
+int rd_size = CONFIG_BLK_DEV_RAM_SIZE;
module_param(rd_nr, int, 0);
MODULE_PARM_DESC(rd_nr, "Maximum number of brd devices");
module_param(rd_size, int, 0);
--
1.5.4.rc2.38.gd6da3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
