From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Steven Noonan <steven@uplinklabs.net>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH] ftrace: fix trace_nop config select
Date: Wed, 29 Oct 2008 17:21:51 +0100 [thread overview]
Message-ID: <20081029162151.GA12529@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0810291113500.2865@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> The trace_nop is the tracer that is defined when no tracer is set in
> the ftrace infrastructure.
>
> The trace_nop was mistakenly selected by HAVE_FTRACE due to the confusion
> between ftrace infrastructure and the ftrace function tracer (which has
> been solved by renaming the function tracer).
>
> This patch changes the select to the approriate TRACING.
>
> This patch should fix compile errors on architectures that do not define
> the FUNCTION_TRACER.
>
> Signed-off-by: Steven Rostedt <srostedt@redhat.com>
> ---
> kernel/trace/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
applied to tip/tracing/urgent, thanks Steve!
Ingo
next prev parent reply other threads:[~2008-10-29 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200810281802.m9SI2fYX030138@hera.kernel.org>
2008-10-29 9:18 ` ftrace: fix depends Heiko Carstens
2008-10-29 15:15 ` [PATCH] ftrace: fix trace_nop config select Steven Rostedt
2008-10-29 16:21 ` Ingo Molnar [this message]
2008-10-30 1:43 ` [PATCH][RFC] x86: add non x86 build configuration Steven Rostedt
2008-10-30 19:51 ` Ingo Molnar
2008-10-30 20:05 ` Steven Rostedt
2008-10-30 20:57 ` Ingo Molnar
2008-10-30 21:09 ` Steven Rostedt
2008-10-30 20:20 ` Sam Ravnborg
2008-10-30 20:55 ` Ingo Molnar
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=20081029162151.GA12529@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=steven@uplinklabs.net \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®