public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 1/5] tracing/events: enable code with EVENT_TRACING not EVENT_TRACER
Date: Fri, 17 Apr 2009 17:11:36 -0400	[thread overview]
Message-ID: <20090417211230.723241189@goodmis.org> (raw)
In-Reply-To: 20090417211135.408179566@goodmis.org

[-- Attachment #1: 0001-tracing-events-enable-code-with-EVENT_TRACING-not-E.patch --]
[-- Type: text/plain, Size: 923 bytes --]

From: Steven Rostedt <srostedt@redhat.com>

The CONFIG_EVENT_TRACER is the way to turn on event tracing when no
other tracing has been configured. All code to get enabled should
depend on CONFIG_EVENT_TRACING. That is what is enabled when TRACING
(or CONFIG_EVENT_TRACER) is selected.

This patch enables the include/trace/ftrace.h file when
CONFIG_EVENT_TRACING is enabled.

[ Impact: fix warning in event tracer selftest ]

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
 include/trace/define_trace.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/include/trace/define_trace.h b/include/trace/define_trace.h
index 1886941..7f1f23d 100644
--- a/include/trace/define_trace.h
+++ b/include/trace/define_trace.h
@@ -56,7 +56,7 @@
 
 #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
 
-#ifdef CONFIG_EVENT_TRACER
+#ifdef CONFIG_EVENT_TRACING
 #include <trace/ftrace.h>
 #endif
 
-- 
1.6.2.1

-- 

  reply	other threads:[~2009-04-17 21:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 21:11 [PATCH 0/5] [GIT PULL] tracing,lockdep,x86: more updates for tip Steven Rostedt
2009-04-17 21:11 ` Steven Rostedt [this message]
2009-04-18  7:13   ` [PATCH 1/5] tracing/events: enable code with EVENT_TRACING not EVENT_TRACER Ingo Molnar
2009-04-18 14:18     ` Steven Rostedt
2009-04-17 21:11 ` [PATCH 2/5] tracing: add EXPORT_SYMBOL_GPL for trace commits Steven Rostedt
2009-04-17 21:11 ` [PATCH 3/5] tracing: add same level recursion detection Steven Rostedt
2009-04-18  7:11   ` Ingo Molnar
2009-04-18 14:12     ` Steven Rostedt
2009-04-17 21:11 ` [PATCH 4/5] tracing: protect trace_printk from recursion Steven Rostedt
2009-04-17 21:11 ` [PATCH 5/5] lockdep,x86: account for irqs enabled in paranoid_exit Steven Rostedt
2009-04-18  7:00   ` 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=20090417211230.723241189@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox