From: Michal Simek <monstr@monstr.eu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Revert "irq: Add tracepoint to softirq_raise" - microblaze build
Date: Wed, 09 Mar 2011 18:01:27 +0100 [thread overview]
Message-ID: <4D77B267.3020307@monstr.eu> (raw)
In-Reply-To: <1299689179.15854.255.camel@gandalf.stny.rr.com>
Steven Rostedt wrote:
> On Wed, 2011-03-09 at 13:20 +0100, Michal Simek wrote:
>> Hi Frederic,
>>
>> I have compiled ftrace support for Microblaze and I have reached a compilation failure.
>>
>> I bisected it and I found that
>> "irq: Add tracepoint to softirq_raise"
>> (sha1:2bf2160d8805de64308e2e7c3cd97813cb58ed2f)
>> caused it.
>>
>> I also found one thread which could be related.
>> http://kerneltrap.org/mailarchive/linux-kernel/2010/9/8/4616941
>>
>> It is likely any missing header or so.
>>
>> Do you know what can be wrong?
>>
>> Thanks,
>> Michal
>>
>>
>> [ALL ] CC kernel/trace/power-traces.o
>> [ALL ] In file included from
>> /mnt/projects/petalinux-v1.00-devel/software/linux-2.6.x/arch/microblaze/include/asm/irq.h:15,
>
> Is there a reason that arch/microblaze/include/asm/irq.h includes
> "linux/interrupt.h"?
Yep, it is. I tried to add some headers not remove them.
Thanks,
Michal
P.S.: Do you want to create proper patch? If not, I will do it.
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2011-03-09 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 12:20 Revert "irq: Add tracepoint to softirq_raise" - microblaze build Michal Simek
2011-03-09 16:46 ` Steven Rostedt
2011-03-09 17:01 ` Michal Simek [this message]
2011-03-09 17:12 ` Steven Rostedt
2011-03-09 17:36 ` Michal Simek
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=4D77B267.3020307@monstr.eu \
--to=monstr@monstr.eu \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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