All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.73-mm3 `highmem_start_page' undeclared  with DEBUG_PAGEALLOC and no highmem
Date: Wed, 02 Jul 2003 11:10:09 +0200	[thread overview]
Message-ID: <3F02A171.7070200@aitel.hist.no> (raw)
In-Reply-To: 20030701203830.19ba9328.akpm@digeo.com

This didn't compile.

.
.
.
   CC      arch/i386/mm/fault.o
   CC      arch/i386/mm/ioremap.o
   CC      arch/i386/mm/extable.o
   CC      arch/i386/mm/pageattr.o
arch/i386/mm/pageattr.c: In function `kernel_map_pages':
arch/i386/mm/pageattr.c:200: `highmem_start_page' undeclared (first use 
in this function)
arch/i386/mm/pageattr.c:200: (Each undeclared identifier is reported 
only once
arch/i386/mm/pageattr.c:200: for each function it appears in.)
make[1]: *** [arch/i386/mm/pageattr.o] Error 1
make: *** [arch/i386/mm] Error 2


Configuring highmem support to 4G instead of turning
it off avoids this, but I have only 512M in
this machine.

Turning off highmem and page allocation debugging
also compiles.

Helge Hafting


WARNING: multiple messages have this Message-ID (diff)
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.73-mm3 `highmem_start_page' undeclared  with DEBUG_PAGEALLOC and no highmem
Date: Wed, 02 Jul 2003 11:10:09 +0200	[thread overview]
Message-ID: <3F02A171.7070200@aitel.hist.no> (raw)
In-Reply-To: 20030701203830.19ba9328.akpm@digeo.com

This didn't compile.

.
.
.
   CC      arch/i386/mm/fault.o
   CC      arch/i386/mm/ioremap.o
   CC      arch/i386/mm/extable.o
   CC      arch/i386/mm/pageattr.o
arch/i386/mm/pageattr.c: In function `kernel_map_pages':
arch/i386/mm/pageattr.c:200: `highmem_start_page' undeclared (first use 
in this function)
arch/i386/mm/pageattr.c:200: (Each undeclared identifier is reported 
only once
arch/i386/mm/pageattr.c:200: for each function it appears in.)
make[1]: *** [arch/i386/mm/pageattr.o] Error 1
make: *** [arch/i386/mm] Error 2


Configuring highmem support to 4G instead of turning
it off avoids this, but I have only 512M in
this machine.

Turning off highmem and page allocation debugging
also compiles.

Helge Hafting

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2003-07-02  8:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02  3:38 2.5.73-mm3 Andrew Morton
2003-07-02  3:38 ` 2.5.73-mm3 Andrew Morton
2003-07-02  5:07 ` 2.5.73-mm3 Martin J. Bligh
2003-07-02  5:07   ` 2.5.73-mm3 Martin J. Bligh
2003-07-02  5:18   ` 2.5.73-mm3 Andrew Morton
2003-07-02  5:18     ` 2.5.73-mm3 Andrew Morton
2003-07-02 18:12     ` 2.5.73-mm3 Martin J. Bligh
2003-07-02 18:12       ` 2.5.73-mm3 Martin J. Bligh
2003-07-02 18:50       ` 2.5.73-mm3 Martin J. Bligh
2003-07-02 18:50         ` 2.5.73-mm3 Martin J. Bligh
2003-07-02 19:56     ` 2.5.73-mm3 Martin J. Bligh
2003-07-02 19:56       ` 2.5.73-mm3 Martin J. Bligh
2003-07-02  9:10 ` Helge Hafting [this message]
2003-07-02  9:10   ` 2.5.73-mm3 `highmem_start_page' undeclared with DEBUG_PAGEALLOC and no highmem Helge Hafting
2003-07-02 10:54 ` 2.5.73-mm3 Maneesh Soni
2003-07-02 10:54   ` 2.5.73-mm3 Maneesh Soni
2003-07-02 15:18   ` 2.5.73-mm3 Andrew Morton
2003-07-02 15:18     ` 2.5.73-mm3 Andrew Morton
2003-07-02 18:27 ` 2.5.73-mm3 Valdis.Kletnieks
2003-07-10  2:11 ` 2.5.73-mm3 vs. linux-2.5.74-mm1 Piet Delaney
2003-07-10  2:11   ` Piet Delaney
2003-07-10  2:32   ` Piet Delaney
2003-07-10  2:32     ` Piet Delaney
2003-07-10  3:13     ` Piet Delaney
2003-07-10  3:13       ` Piet Delaney
2003-07-10  3:13     ` Piet Delaney
2003-07-10  3:13       ` Piet Delaney

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=3F02A171.7070200@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.