From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Clausen <clausen@melbourne.sgi.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: [patch] bogus ramdisk sanity check on ip27
Date: Fri, 21 Feb 2003 04:12:42 +0100 [thread overview]
Message-ID: <20030221041242.B19392@linux-mips.org> (raw)
In-Reply-To: <20030220003839.GF915@pureza.melbourne.sgi.com>; from clausen@melbourne.sgi.com on Thu, Feb 20, 2003 at 11:38:39AM +1100
On Thu, Feb 20, 2003 at 11:38:39AM +1100, Andrew Clausen wrote:
> There is currently a check that the ramdisk image resides at a sane
> memory address, below "max_pfn". However, max_pfn isn't initialized
> (and apparently isn't relevant) for ip27. The only assignments to
> max_pfn lie inside #ifndef CONFIG_SGI_IP27.
>
> Therefore, this test is bogus, so here's a patch to
> #ifndef CONFIG_SGI_IP27 it.
>
> This patch applies cleanly on 2.4.x and 2.5.x (at a different offset).
No winner in a beauty contest but I think it's ok until we sort the
underlying NUMA issues which we'd have to do anyway at some point -
more ccNUMA stuff will come eventually ...
Ralf
prev parent reply other threads:[~2003-02-21 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 0:38 [patch] bogus ramdisk sanity check on ip27 Andrew Clausen
2003-02-21 3:12 ` 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=20030221041242.B19392@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=clausen@melbourne.sgi.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