From: Ralf Baechle <ralf@linux-mips.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Kumba <kumba@gentoo.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH]: Rewrite of arch/mips/ramdisk/
Date: Wed, 17 Nov 2004 14:17:41 +0100 [thread overview]
Message-ID: <20041117131741.GA23041@linux-mips.org> (raw)
In-Reply-To: <20041115180507.GA23952@lst.de>
On Mon, Nov 15, 2004 at 07:05:07PM +0100, Christoph Hellwig wrote:
> You could include a loop-back mountable filesystem image. But that's
> not even nessecary. The kernel will call /init of the files in the
> initramfs, and you could just store everything you'd store in the
> loopback filesystem directly in the initramfs image.
Right. So this means CONFIG_EMBEDDED_RAMDISK and
CONFIG_EMBEDDED_RAMDISK_IMAGE have become obsolete. So unless somebody
delivers a convincing argument I'm going to remove these options.
Ralf
prev parent reply other threads:[~2004-11-17 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 6:43 [PATCH]: Rewrite of arch/mips/ramdisk/ Kumba
2004-11-14 8:52 ` Christoph Hellwig
2004-11-14 17:25 ` Kumba
2004-11-14 19:31 ` Kumba
2004-11-15 17:55 ` Ralf Baechle
2004-11-16 1:21 ` Kumba
2004-11-15 18:05 ` Christoph Hellwig
2004-11-17 13:17 ` Ralf Baechle [this message]
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=20041117131741.GA23041@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=hch@lst.de \
--cc=kumba@gentoo.org \
--cc=linux-mips@linux-mips.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