From: Mauricio Lin <mauriciolin@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc3-mm2: fs/proc/task_mmu.c warnings
Date: Mon, 2 May 2005 18:30:01 -0400 [thread overview]
Message-ID: <3f250c7105050215306de620ac@mail.gmail.com> (raw)
In-Reply-To: <20050501222916.GB3592@stusta.de>
Hi Adrian,
I tried to replicate this warning but I did not get it on vanilla
kernel. I put the config as
CONFIG_HIGHPTE=y
as well, but no warning. Perhaps I have to try it with mm tree. Any comments?
What do you think Andrew?
BR,
Mauricio Lin.
On 5/1/05, Adrian Bunk <bunk@stusta.de> wrote:
> proc-pid-smaps.patch caused the following warnings with
> CONFIG_HIGHPTE=y:
>
> <-- snip -->
>
> ...
> CC fs/proc/task_mmu.o
> fs/proc/task_mmu.c: In function `smaps_pte_range':
> fs/proc/task_mmu.c:177: warning: implicit declaration of function `kmap_atomic'
> fs/proc/task_mmu.c:207: warning: implicit declaration of function `kunmap_atomic'
> ...
>
> <-- snip -->
>
> Unfortunately, I do not understand how to fix this properly.
>
> 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
>
>
next prev parent reply other threads:[~2005-05-02 22:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 23:43 2.6.12-rc3-mm2 Andrew Morton
2005-05-01 0:27 ` 2.6.12-rc3-mm2 Benoit Boissinot
2005-05-01 0:37 ` 2.6.12-rc3-mm2 Andrew Morton
[not found] ` <40f323d00504301753140a7ef4@mail.gmail.com>
2005-05-01 1:12 ` 2.6.12-rc3-mm2 Benoit Boissinot
2005-05-01 2:32 ` 2.6.12-rc3-mm2 - /proc/ide/sr0/model: No such file or directory Jesper Juhl
2005-05-03 3:11 ` Greg KH
2005-05-03 3:18 ` Andrew Morton
2005-05-03 4:48 ` Greg KH
2005-05-03 7:11 ` Bartlomiej Zolnierkiewicz
2005-05-03 18:27 ` Greg KH
2005-05-01 3:30 ` [patch] alternative fix for VFS race (was Re: 2.6.12-rc3-mm2) Nick Piggin
2005-05-01 12:56 ` 2.6.12-rc3-mm2: ACPI problems Rafael J. Wysocki
2005-05-01 13:41 ` Brice Goglin
2005-05-01 15:07 ` 2.6.12-rc3-mm2 - kswapd0 keeps running Damir Perisa
2005-05-01 22:06 ` Andrew Morton
2005-05-02 6:01 ` Damir Perisa
2005-05-02 15:31 ` Damir Perisa
2005-05-02 18:14 ` Andrew Morton
2005-05-02 21:30 ` Damir Perisa
2005-05-06 18:07 ` Damir Perisa
2005-05-04 19:12 ` Cameron Harris
2005-05-04 21:47 ` Damir Perisa
2005-05-01 15:08 ` 2.6.12-rc3-mm2: ppc pte_offset_map() Sean Neakums
2005-05-01 15:50 ` Jesper Juhl
2005-05-01 22:46 ` Andrew Morton
2005-05-01 23:01 ` Jesper Juhl
2005-05-03 22:04 ` cliff white
2005-05-02 10:14 ` Hugh Dickins
2005-05-01 22:29 ` 2.6.12-rc3-mm2: fs/proc/task_mmu.c warnings Adrian Bunk
2005-05-02 22:30 ` Mauricio Lin [this message]
2005-05-02 23:35 ` Mauricio Lin
2005-05-02 23:45 ` Andrew Morton
2005-05-02 23:56 ` Mauricio Lin
2005-05-03 20:16 ` cliff white
2005-05-03 22:12 ` Mauricio Lin
2005-05-03 18:02 ` Cliff White
2005-05-02 5:07 ` 2.6.12-rc3-mm2 James Cloos
2005-05-02 5:26 ` 2.6.12-rc3-mm2 Andrew Morton
2005-04-30 21:34 ` 2.6.12-rc3-mm2 Diego Calleja
2005-05-03 16:08 ` 2.6.12-rc3-mm2 Bill Davidsen
2005-05-03 13:37 ` 2.6.12-rc3-mm2 Barry K. Nathan
2005-05-04 15:12 ` 2.6.12-rc3-mm2 Christoph Hellwig
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=3f250c7105050215306de620ac@mail.gmail.com \
--to=mauriciolin@gmail.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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