From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: imx: add missing include of linux/ftrace.h
Date: Sat, 8 Oct 2011 16:33:24 +0100 [thread overview]
Message-ID: <20111008153324.GA18424@gallagher> (raw)
In-Reply-To: <1928841.IC5oQhqc6l@wuerfel>
Hi Arnd, Sascha,
On Sat, Oct 08, 2011 at 05:16:26PM +0200, Arnd Bergmann wrote:
> Using the __exception_irq_entry symbol requires including
> this header file:
>
> arch/arm/plat-mxc/avic.c:154:39: error: expected '=', ',', ';', 'asm'
> or '__attribute__' before 'avic_handle_irq'
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> arch/arm/plat-mxc/avic.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/plat-mxc/avic.c b/arch/arm/plat-mxc/avic.c
> index 8875fb4..9bab263 100644
> --- a/arch/arm/plat-mxc/avic.c
> +++ b/arch/arm/plat-mxc/avic.c
> @@ -20,6 +20,7 @@
> #include <linux/module.h>
> #include <linux/irq.h>
> #include <linux/io.h>
> +#include <linux/ftrace.h>
Russell has applied a patch to move __exception_irq_entry into
asm/exception.h (with the include of ftrace.h) into his for-next branch.
So I think avic.c should be using this (as it's not explicitly using
ftrace).
Jamie
next prev parent reply other threads:[~2011-10-08 15:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 9:20 [PULL] i.MX Sascha Hauer
2011-10-07 20:30 ` Arnd Bergmann
2011-10-08 10:13 ` Sascha Hauer
2011-10-08 15:14 ` Arnd Bergmann
2011-10-08 15:15 ` [PATCH 1/3] ARM: imx: always select CACHE_L2X0 on i.MX3 Arnd Bergmann
2011-10-09 5:39 ` Shawn Guo
2011-10-09 5:44 ` Barry Song
2011-10-08 15:16 ` [PATCH 2/3] ARM: imx: add missing include of linux/ftrace.h Arnd Bergmann
2011-10-08 15:33 ` Jamie Iles [this message]
2011-10-08 15:16 ` [PATCH 3/7] ARM: imx: export imx_ioremap Arnd Bergmann
2011-10-09 5:49 ` Shawn Guo
2011-10-09 9:33 ` [PULL] i.MX Sascha Hauer
2011-10-10 6:36 ` Uwe Kleine-König
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=20111008153324.GA18424@gallagher \
--to=jamie@jamieiles.com \
--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).