public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
	srostedt@redhat.com, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:tracing/ftrace] tracing, power-trace: make it build even if the power-tracer is turned off
Date: Fri, 6 Mar 2009 11:51:23 GMT	[thread overview]
Message-ID: <tip-af438c0f114b6f731b923b5c07150f6159471502@git.kernel.org> (raw)
In-Reply-To: <20090306104106.GF31042@elte.hu>

Commit-ID:  af438c0f114b6f731b923b5c07150f6159471502
Gitweb:     http://git.kernel.org/tip/af438c0f114b6f731b923b5c07150f6159471502
Author:     "Ingo Molnar" <mingo@elte.hu>
AuthorDate: Fri, 6 Mar 2009 12:47:08 +0100
Commit:     Ingo Molnar <mingo@elte.hu>
CommitDate: Fri, 6 Mar 2009 12:47:08 +0100

tracing, power-trace: make it build even if the power-tracer is turned off

Impact: build fix

The 'struct power_trace' definition is needed (for the event tracer) even if
the power-tracer plugin is turned off in the .config.

Cc: Steven Rostedt <srostedt@redhat.com>
LKML-Reference: <20090306104106.GF31042@elte.hu>
Signed-off-by: Ingo Molnar <mingo@elte.hu>


---
 include/trace/power.h |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/include/trace/power.h b/include/trace/power.h
index 2c733e5..38aca53 100644
--- a/include/trace/power.h
+++ b/include/trace/power.h
@@ -11,12 +11,10 @@ enum {
 };
 
 struct power_trace {
-#ifdef CONFIG_POWER_TRACER
 	ktime_t			stamp;
 	ktime_t			end;
 	int			type;
 	int			state;
-#endif
 };
 
 DECLARE_TRACE(power_start,

      reply	other threads:[~2009-03-06 11:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  3:18 [PATCH 0/3] [GIT PULL] for tip/tracing/ftrace Steven Rostedt
2009-03-06  3:18 ` [PATCH 1/3] tracing: make all file_operations const Steven Rostedt
2009-03-06  3:18 ` [PATCH 2/3] tracing: move print of event format to separate file Steven Rostedt
2009-03-06  3:19 ` [PATCH 3/3] tracing: add format files for ftrace default entries Steven Rostedt
2009-03-06 10:41 ` [PATCH 0/3] [GIT PULL] for tip/tracing/ftrace Ingo Molnar
2009-03-06 11:51   ` Ingo Molnar [this message]

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=tip-af438c0f114b6f731b923b5c07150f6159471502@git.kernel.org \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=srostedt@redhat.com \
    --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