From: Arjan van de Ven <arjan@linux.intel.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: fix TRACE_EVENT power tracepoint creation (v2)
Date: Thu, 28 Oct 2010 08:33:06 -0700 [thread overview]
Message-ID: <4CC997B2.1060002@linux.intel.com> (raw)
In-Reply-To: <20101028153117.GA4051@Krystal>
On 10/28/2010 8:31 AM, Mathieu Desnoyers wrote:
> DEFINE_TRACE should also exist when CONFIG_EVENT_TRACING=n. Otherwise, setting
> only TRACEPOINTS=y is broken.
>
> Changelog since v1:
> - Only change the makefiles, as required.
> - Patch based on 2.6.36 mainline kernel.
>
> Signed-off-by: Mathieu Desnoyers<mathieu.desnoyers@efficios.com>
> CC: Arjan van de Ven<arjan@linux.intel.com>
> CC: Steven Rostedt<rostedt@goodmis.org>
Acked-by: Arjan van de Ven <arjan@linux.intel.com>
next prev parent reply other threads:[~2010-10-28 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 15:31 [PATCH] tracing: fix TRACE_EVENT power tracepoint creation (v2) Mathieu Desnoyers
2010-10-28 15:33 ` Arjan van de Ven [this message]
2011-01-09 21:12 ` [tip:perf/urgent] tracing: Fix TRACE_EVENT power tracepoint creation tip-bot for Mathieu Desnoyers
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=4CC997B2.1060002@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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