From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 0/3] [GIT PULL] tracing: rebase of TRACE_EVENT_TEMPLATE
Date: Wed, 25 Nov 2009 09:03:42 +0100 [thread overview]
Message-ID: <20091125080342.GA20495@elte.hu> (raw)
In-Reply-To: <20091125043811.603607335@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Ingo,
>
> This is the rebase to resolve the conflicts with perf.
>
> Please pull the latest tip/perf/core tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/perf/core
>
>
> Steven Rostedt (3):
> tracing: Create new TRACE_EVENT_TEMPLATE
> tracing: Create new DEFINE_EVENT_PRINT
> tracing: Convert some sched trace events to DEFINE_EVENT and _PRINT
>
> ----
> include/linux/tracepoint.h | 6 +
> include/trace/define_trace.h | 11 ++
> include/trace/events/sched.h | 170 ++++++++-------------------
> include/trace/ftrace.h | 266 +++++++++++++++++++++++++++++++++++-------
> 4 files changed, 292 insertions(+), 161 deletions(-)
Pulled, thanks a lot Steve!
Ingo
next prev parent reply other threads:[~2009-11-25 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 4:38 [PATCH 0/3] [GIT PULL] tracing: rebase of TRACE_EVENT_TEMPLATE Steven Rostedt
2009-11-25 4:38 ` [PATCH 1/3] [PATCH 1/3] tracing: Create new TRACE_EVENT_TEMPLATE Steven Rostedt
2009-11-25 4:38 ` [PATCH 2/3] [PATCH 2/3] tracing: Create new DEFINE_EVENT_PRINT Steven Rostedt
2009-11-25 4:38 ` [PATCH 3/3] [PATCH 3/3] tracing: Convert some sched trace events to DEFINE_EVENT and _PRINT Steven Rostedt
2009-11-25 8:03 ` Ingo Molnar [this message]
2009-11-25 12:12 ` [PATCH 0/3] [GIT PULL] tracing: rebase of TRACE_EVENT_TEMPLATE Frederic Weisbecker
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=20091125080342.GA20495@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--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