From: rkuo <rkuo@codeaurora.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hexagon@vger.kernel.org, linux-kernel@vger.kernel.org,
Kevin Cernekee <cernekee@gmail.com>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH] hexagon: Fix build failures in linux-next
Date: Tue, 9 Dec 2014 18:25:23 -0600 [thread overview]
Message-ID: <20141210002523.GA17946@codeaurora.org> (raw)
In-Reply-To: <1418163705-1816-1-git-send-email-linux@roeck-us.net>
On Tue, Dec 09, 2014 at 02:21:45PM -0800, Guenter Roeck wrote:
> hexagon:defconfig fails to build in linux-next since commit 332fd7c4fef5
> ("genirq: Generic chip: Change irq_reg_{readl,writel} arguments").
>
> The primary build failure is
>
> arch/hexagon/include/asm/cacheflush.h: In function 'copy_to_user_page':
> arch/hexagon/include/asm/cacheflush.h:89:22: error: 'VM_EXEC' undeclared
>
> This is the result of including of <linux/io.h> from <linux/irq.h>,
> which is now necessary due to the use of readl and writel from irq.h.
> This causes recursive inclusions in hexagon code; cacheflush.h is included
> from mm.h prior to the definition of VM_EXEC.
>
> Fix the problem by moving copy_to_user_page from the hexagon include file to
> arch/hexagon/mm/cache.c, similar to other architectures. After this change,
> several redefinitions of readl and writel are reported. Those are caused
> by recursive inclusions of io.h and asm/cacheflush.h. Fix those problems by
> reducing the number of files included from those files. Also, it was necessary
> to stop including asm-generic/cacheflush.h from asm/cacheflush.h. Instead,
> functionality originally provided by asm-generic/cacheflush.h is now coded
> in asm/cacheflush.h directly.
>
> Cc: Kevin Cernekee <cernekee@gmail.com>
> Cc: Jason Cooper <jason@lakedaemon.net>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> Compile tested only. Applies to linux-next as well as mainline.
>
> arch/hexagon/include/asm/cacheflush.h | 36 ++++++++++++++++++-----------------
> arch/hexagon/include/asm/io.h | 5 -----
> arch/hexagon/kernel/setup.c | 1 +
> arch/hexagon/mm/cache.c | 10 ++++++++++
> arch/hexagon/mm/ioremap.c | 1 +
> 5 files changed, 31 insertions(+), 22 deletions(-)
>
Thanks for the cleanup; tested working on hardware.
I'm fine taking this into my tree, or it can go via another tree if more
expedient.
Acked-by: Richard Kuo <rkuo@codeaurora.org>
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2014-12-10 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 22:21 [PATCH] hexagon: Fix build failures in linux-next Guenter Roeck
2014-12-10 0:25 ` rkuo [this message]
2014-12-10 3:13 ` Guenter Roeck
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=20141210002523.GA17946@codeaurora.org \
--to=rkuo@codeaurora.org \
--cc=cernekee@gmail.com \
--cc=jason@lakedaemon.net \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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.