From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: fix arch/arm/mm/copypage-v6.c build
Date: Mon, 21 Dec 2009 23:35:59 +0000 [thread overview]
Message-ID: <20091221233559.GC28541@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4B2DE16E.4050708@compulab.co.il>
On Sun, Dec 20, 2009 at 10:33:50AM +0200, Mike Rapoport wrote:
> Commit 115b22474eb1905da2f606a057da3455833333d3 (ARM: 5794/1: Flush the
> D-cache during copy_user_highpage()) breaks build for ARM v7:
>
> CC arch/arm/mm/copypage-v6.o
> arch/arm/mm/copypage-v6.c: In function'v6_copy_user_highpage_nonaliasing':
> arch/arm/mm/copypage-v6.c:51: error: implicit declaration of function '__cpuc_flush_dcache_page'
> make[2]: *** [arch/arm/mm/copypage-v6.o] Error 1
This one's already been caught.
prev parent reply other threads:[~2009-12-21 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-20 8:33 [PATCH] ARM: fix arch/arm/mm/copypage-v6.c build Mike Rapoport
2009-12-21 23:35 ` Russell King - ARM Linux [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=20091221233559.GC28541@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).