[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c62985530810230924q7f5bd48es3353428766ee49eb@mail.gmail.com>
Date: Thu, 23 Oct 2008 18:24:14 +0200
From: "Frédéric Weisbecker" <fweisbec@...il.com>
To: "Ingo Molnar" <mingo@...e.hu>
Cc: "Geert Uytterhoeven" <geert@...ux-m68k.org>,
"Alexey Dobriyan" <adobriyan@...il.com>,
"Stephen Rothwell" <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
"Steven Rostedt" <rostedt@...dmis.org>
Subject: Re: [PATCH] tracing: fix a build error on alpha and m68k
2008/10/23 Frederic Weisbecker <fweisbec@...il.com>:
> When tracing is enabled, some arch have included <linux/irqflags.h>
> on their <asm/system.h> but others like alpha or m68k don't.
>
> Build error on alpha:
>
> kernel/trace/trace.c: In function 'tracing_generic_entry_update':
> kernel/trace/trace.c:658: error: implicit declaration of function 'irqs_disabled_flags'
> kernel/trace/trace.c: In function 'tracing_cpumask_write':
> kernel/trace/trace.c:2145: error: implicit declaration of function 'raw_local_irq_disable'
> kernel/trace/trace.c:2162: error: implicit declaration of function 'raw_local_irq_enable'
> kernel/trace/trace.c: In function 'trace_die_handler':
> kernel/trace/trace.c:3039: error: 'DIE_OOPS' undeclared (first use in this function)
>
> Build error on m68k:
> http://kisskb.ellerman.id.au/kisskb/buildresult/50641/
>
>
> Include it on kernel/trace/trace.c
>
> Reported-by: Alexey Dobriyan <adobriyan@...il.com>
> Signed-off-by: Frederic Weisbecker <fweisbec@...il.com>
> ---
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 78d5661..deb9684 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -34,6 +34,7 @@
>
> #include <linux/stacktrace.h>
> #include <linux/ring_buffer.h>
> +#include <linux/irqflags.h>
>
> #include "trace.h"
>
>
And one other "reported by" for the m68k error:
Reported-by: Geert Uytterhoeven <geert@...ux-m68k.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists