From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 0/2 v2] [GIT PULL][v3.2] tracing: queued updates
Date: Thu, 13 Oct 2011 10:59:39 +0200 [thread overview]
Message-ID: <20111013085936.GA13046@elte.hu> (raw)
In-Reply-To: <20111012162320.GA31857@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> Tests are also looking good so far.
there's a cross-build failure on the m32r architecture:
/home/mingo/tip/kernel/trace/trace_clock.c:117: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'trace_counter'
/home/mingo/tip/kernel/trace/trace_clock.c: In function 'trace_clock_counter':
/home/mingo/tip/kernel/trace/trace_clock.c:126: error: implicit declaration of function 'atomic64_add_return'
/home/mingo/tip/kernel/trace/trace_clock.c:126: error: 'trace_counter' undeclared (first use in this function)
/home/mingo/tip/kernel/trace/trace_clock.c:126: error: (Each undeclared identifier is reported only once
/home/mingo/tip/kernel/trace/trace_clock.c:126: error: for each function it appears in.)
Thanks,
Ingo
next prev parent reply other threads:[~2011-10-13 9:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 15:20 [PATCH 0/2 v2] [GIT PULL][v3.2] tracing: queued updates Steven Rostedt
2011-10-11 15:20 ` [PATCH 1/2 v2] tracing: Warn on output if the function tracer was found corrupted Steven Rostedt
2011-10-11 15:20 ` [PATCH 2/2 v2] tracing: Do not allocate buffer for trace_marker Steven Rostedt
2011-10-12 8:16 ` [PATCH 0/2 v2] [GIT PULL][v3.2] tracing: queued updates Ingo Molnar
2011-10-12 11:21 ` Steven Rostedt
2011-10-12 13:26 ` Steven Rostedt
2011-10-12 16:23 ` Ingo Molnar
2011-10-12 16:32 ` Steven Rostedt
2011-10-13 8:59 ` Ingo Molnar [this message]
2011-10-13 13:55 ` Steven Rostedt
2011-10-13 14:00 ` Steven Rostedt
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=20111013085936.GA13046@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.