public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Jurriaan <thunder7@xs4all.nl>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-mm2 fremap.c compile error
Date: Fri, 11 Mar 2005 23:50:08 +0100	[thread overview]
Message-ID: <20050311225008.GP3723@stusta.de> (raw)
In-Reply-To: <20050308185411.GA17977@middle.of.nowhere>

On Tue, Mar 08, 2005 at 07:54:11PM +0100, Jurriaan wrote:

> mm/fremap.c:33:48: macro "flush_cache_page" passed 3 arguments, but takes just 2
> mm/fremap.c: In function `zap_pte':
> mm/fremap.c:33: error: `flush_cache_page' undeclared (first use in this function)
> mm/fremap.c:33: error: (Each undeclared identifier is reported only once
> mm/fremap.c:33: error: for each function it appears in.)
> mm/fremap.c:34:55: macro "ptep_get_and_clear" passed 3 arguments, but takes just 1
> mm/fremap.c:34: error: `ptep_get_and_clear' undeclared (first use in this function)
> mm/fremap.c:48:41: macro "pte_clear" passed 3 arguments, but takes just 1
> mm/fremap.c:48: error: `pte_clear' undeclared (first use in this function)
> mm/fremap.c: In function `install_page':
> mm/fremap.c:97: warning: implicit declaration of function `set_pte_at'
> make[1]: *** [mm/fremap.o] Error 1
> make: *** [mm] Error 2
>  
> The same config worked fine for 2.6.11-mm1:
>...

I wasn't able to reproduce this with your .config .

Are you using a completely otherwise unpatched 2.6.11-mm2?
Please retry with a freshly unpacked 2.6.11 plus the -mm2 patch.

> Good luck,
> Jurriaan

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-03-11 22:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 11:38 2.6.11-mm2 Andrew Morton
2005-03-08 13:58 ` 2.6.11-mm2 Paul Mundt
2005-03-08 19:40   ` 2.6.11-mm2 Andrew Morton
2005-03-08 16:00 ` 2.6.11-mm2 (compile stats) John Cherry
2005-03-08 18:54 ` 2.6.11-mm2 fremap.c compile error Jurriaan
2005-03-11 22:50   ` Adrian Bunk [this message]
2005-03-08 19:29 ` inconsistent kallsyms data [2.6.11-mm2] Dominik Brodowski
2005-03-08 20:35   ` Andrew Morton
2005-03-08 20:45     ` Dominik Brodowski
2005-03-09 12:57       ` Paulo Marques
2005-03-09 20:16         ` Paulo Marques
2005-03-10 12:12           ` Paulo Marques
2005-03-13  8:54             ` Sam Ravnborg
2005-03-14 13:33               ` Paulo Marques
2005-03-14 22:17               ` Dominik Brodowski
2005-03-14 22:14             ` Dominik Brodowski
2005-03-08 23:20 ` 2.6.11-mm2 Christoph Hellwig
2005-03-08 23:29   ` 2.6.11-mm2 Andrew Morton
2005-03-08 23:36 ` 2.6.11-mm2 J.A. Magallon
2005-03-08 23:44   ` 2.6.11-mm2 Robert Love
2005-03-08 23:51     ` 2.6.11-mm2 J.A. Magallon
2005-03-09  0:02       ` 2.6.11-mm2 Robert Love
2005-03-09  0:16 ` 2.6.11-mm2 Adrian Bunk
2005-03-09  0:53   ` 2.6.11-mm2 Andrew Morton
2005-03-09  1:39     ` 2.6.11-mm2 Jeff Garzik
2005-03-09  0:20 ` 2.6.11-mm2 Adrian Bunk
2005-03-09  1:50   ` 2.6.11-mm2 Karsten Keil
2005-03-10  7:57 ` 2.6.11-mm2 Stefano Rivoir
2005-03-10  8:09   ` 2.6.11-mm2 Andrew Morton
2005-03-21 23:45   ` 2.6.11-mm2 Andrew Morton

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=20050311225008.GP3723@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder7@xs4all.nl \
    /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