From: Randy Dunlap <rdunlap@xenotime.net>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-parisc@vger.kernel.org,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: compile failure on hppa64: pte_mkwrite
Date: Fri, 14 Jan 2011 15:15:59 -0800 [thread overview]
Message-ID: <4D30D92F.20106@xenotime.net> (raw)
In-Reply-To: <alpine.SOC.1.00.1101150057210.8462@math.ut.ee>
On 01/14/11 14:59, Meelis Roos wrote:
> Tried todays 2.6.37+git on hppa64 and it fail to compile:
>
> CC arch/parisc/kernel/asm-offsets.s
> In file included from /home/mroos/linux-2.6/arch/parisc/include/asm/pgtable.h:13,
> from arch/parisc/kernel/asm-offsets.c:37:
> include/linux/mm.h: In function 'maybe_mkwrite':
> include/linux/mm.h:482: error: implicit declaration of function 'pte_mkwrite'
> include/linux/mm.h:482: error: incompatible types when assigning to type 'pte_t' from type 'int'
> In file included from arch/parisc/kernel/asm-offsets.c:37:
> /home/mroos/linux-2.6/arch/parisc/include/asm/pgtable.h: At top level:
> /home/mroos/linux-2.6/arch/parisc/include/asm/pgtable.h:338: error: conflicting types for 'pte_mkwrite'
> include/linux/mm.h:482: note: previous implicit declaration of 'pte_mkwrite' was here
> make[1]: *** [arch/parisc/kernel/asm-offsets.s] Error 1
> make: *** [prepare0] Error 2
>
> It seems pte_mkwrite is referenced in mm.h but not defined anywhere in
> include directory.
>
James posted a patch:
http://marc.info/?l=linux-parisc&m=129504371532124&w=2
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-01-14 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 22:59 compile failure on hppa64: pte_mkwrite Meelis Roos
2011-01-14 23:15 ` Randy Dunlap [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=4D30D92F.20106@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mroos@linux.ee \
/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.