From: Ingo Molnar <mingo@elte•hu>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix•de>,
"H. Peter Anvin" <hpa@zytor•com>,
linux-next@vger•kernel.org, Steven Rostedt <rostedt@goodmis•org>
Subject: Re: linux-next: ftrace tree build failure
Date: Fri, 15 Aug 2008 09:56:14 +0200 [thread overview]
Message-ID: <20080815075614.GA3010@elte.hu> (raw)
In-Reply-To: <20080815122743.9715a5e1.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi all,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> kernel/trace/ftrace.c: In function 'ftrace_record_ip':
> kernel/trace/ftrace.c:345: error: implicit declaration of function 'in_nmi'
>
> Caused by commit 431e94644bde07a327dea17ee9be297c3d44a876 ("ftrace: do
> not trace NMI contexts").
>
> in_nmi() is not defined as a function (or macro) anywhere in my kernel
> tree, so I assume a patch was missed. More care, please.
>
> I reverted the above commit.
hm, it's present in my tree and has been there for a long time:
| commit 0d84b78a606f1562532cd576ee8733caf5a4aed3
| Author: Mathieu Desnoyers <mathieu.desnoyers@polymtl•ca>
| Date: Mon May 12 21:21:07 2008 +0200
|
| x86 NMI-safe INT3 and Page Fault
what happened is that i restructured the integration branches yesterday
and moved the tracing/nmisafe from auto-ftrace-next to auto-latest -
without realizing the dependency. I fixed that now and pushed out the
updated auto-ftrace-next branch.
Ingo
next prev parent reply other threads:[~2008-08-15 7:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 2:27 linux-next: ftrace tree build failure Stephen Rothwell
2008-08-15 7:56 ` Ingo Molnar [this message]
2008-08-15 8:29 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-08-25 3:01 Stephen Rothwell
2008-08-25 6:09 ` Ingo Molnar
2008-08-25 16:42 ` Steven Rostedt
2008-08-25 16:46 ` Steven Rostedt
2008-08-25 3:08 Stephen Rothwell
2008-08-25 6:05 ` Ingo Molnar
2008-08-25 6:11 ` Ingo Molnar
2008-08-25 6:31 ` Stephen Rothwell
2008-11-25 3:07 Stephen Rothwell
2008-11-25 3:21 ` Steven Rostedt
2008-11-25 7:28 ` Ingo Molnar
2008-11-25 7:43 ` Stephen Rothwell
2008-11-25 8:04 ` Ingo Molnar
2008-11-25 14:57 ` John W. Linville
2008-11-25 18:46 ` Luis R. Rodriguez
2008-11-26 0:08 ` Stephen Rothwell
2008-11-26 0:14 ` Luis R. Rodriguez
2008-11-25 3:21 Stephen Rothwell
2008-11-25 3:48 ` Steven Rostedt
2008-11-25 4:13 ` Stephen Rothwell
2008-11-25 4:31 ` Steven Rostedt
2008-11-25 5:09 ` Stephen Rothwell
2008-11-25 5:44 ` Steven Rostedt
2008-11-25 6:57 ` Stephen Rothwell
2008-11-25 7:14 ` Ingo Molnar
2008-11-25 7:26 ` Stephen Rothwell
2008-11-25 5:24 ` Steven Rostedt
2009-01-02 9:07 Stephen Rothwell
2009-01-02 9:14 ` Ingo Molnar
2009-01-02 10:22 ` Stephen Rothwell
2009-01-02 11:16 ` Ingo Molnar
2009-01-07 0:53 Stephen Rothwell
2009-01-07 9:55 ` Ingo Molnar
2009-01-07 21:20 ` Stephen Rothwell
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=20080815075614.GA3010@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=hpa@zytor$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rostedt@goodmis$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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