public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Paul Larson <plars@austin.ibm.com>
Cc: Frank Davis <fdavis@si.rr.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.4.9-ac4: undefined reference pgtable_cache_init
Date: Thu, 30 Aug 2001 23:25:51 +0100	[thread overview]
Message-ID: <20010830232551.J1149@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3B8E6467.1030204@si.rr.com> <20010830172612.F1149@flint.arm.linux.org.uk> <999184657.9362.32.camel@plars.austin.ibm.com>
In-Reply-To: <999184657.9362.32.camel@plars.austin.ibm.com>; from plars@austin.ibm.com on Thu, Aug 30, 2001 at 03:17:36PM +0000

On Thu, Aug 30, 2001 at 03:17:36PM +0000, Paul Larson wrote:
> I've seen this as well on i386.  It crops up when you are using HIGHMEM.
> In include/asm-i386/pgtable.h you declare pgtable_cache_init if HIGHMEM
> is on, or define it to the empty while loop if not.  It really needs to
> be calling init_pae_pgd_cache instead though.  Try this patch against
> 2.4.9-ac4.  I don't know if changing the name of init_pae_pgd_cache was
> the Right Thing (tm) to do, but it worked for me.  It's not getting
> called anywhere else anyways.

It got changed because we don't want to add multiple architecture
specific functions to init/main.c, but rather have one generic call
which any architecture can use for this type of thing.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


      reply	other threads:[~2001-08-30 23:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-30 16:05 2.4.9-ac4: undefined reference pgtable_cache_init Frank Davis
2001-08-30 16:26 ` Russell King
2001-08-30 15:17   ` Paul Larson
2001-08-30 22:25     ` Russell King [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=20010830232551.J1149@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=fdavis@si.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plars@austin.ibm.com \
    /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