[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200712140615.lBE6FX4b058136@www262.sakura.ne.jp>
Date: Fri, 14 Dec 2007 15:15:32 +0900
From: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To: Randy Dunlap <randy.dunlap@...cle.com>
Cc: linux-kernel@...r.kernel.org,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Subject: Re: [2.6.24-rc5-mm1] Why CONFIG_BLK_DEV_RAM=m makes \\\"#ifdef CONFIG_BLK_DEV_RAM\\\" false?
Hello.
Randy Dunlap <randy.dunlap@...cle.com> wrote:
> I don't think that this is a change from the recent past.
Oh, it is my mistake.
I found that choosing CONFIG_BLK_DEV_RAM=m makes
impossible to pass an initrd image since
populate_rootfs() in init/initramfs.c omits
code for checking whether the image is an initrd or not.
But I didn't know CONFIG_BLK_DEV_RAM is tristate.
So, I have to change to CONFIG_BLK_DEV_RAM=y when
I want to pass an initrd image after "make allmodconfig".
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists