From: Ralf Baechle <ralf@linux-mips.org>
To: Charlie Brady <charlieb-linux-mips@e-smith.com>
Cc: Dimitri Torfs <dimitri@sonycom.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH][2.6] Fix Makefiles for CONFIG_EMBEDDED_RAMDISK
Date: Fri, 9 Jan 2004 10:07:21 +0100 [thread overview]
Message-ID: <20040109090721.GC16940@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0401071543430.1954-100000@allspice.nssg.mitel.com>
On Wed, Jan 07, 2004 at 03:44:32PM -0500, Charlie Brady wrote:
> > here are patches that fix the arch/mips/Makefile and
> > arch/mips/ramdisk/Makefile when an embedded ramdisk image needs to
> > be included through the CONFIG_EMBEDDED_RAMDISK option.
>
> I'm curious as to why this is a mips specific feature. Does anyone know?
There's little machine dependence as you noticed; just the linker script
would need to be fixed as it's hardwired to mips.
Ralf
prev parent reply other threads:[~2004-01-09 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 20:57 [PATCH][2.6] Fix Makefiles for CONFIG_EMBEDDED_RAMDISK Dimitri Torfs
2004-01-07 20:44 ` Charlie Brady
2004-01-09 9:07 ` 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=20040109090721.GC16940@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=charlieb-linux-mips@e-smith.com \
--cc=dimitri@sonycom.com \
--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