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>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/3] [GIT PULL] for tip/tracing/ftrace
Date: Thu, 05 Mar 2009 22:18:57 -0500 [thread overview]
Message-ID: <20090306031857.686507907@goodmis.org> (raw)
Ingo,
Please pull the latest tip/tracing/ftrace tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/tracing/ftrace
Steven Rostedt (3):
tracing: make all file_operations const
tracing: move print of event format to separate file
tracing: add format files for ftrace default entries
----
kernel/trace/Makefile | 1 +
kernel/trace/ftrace.c | 10 +-
kernel/trace/ring_buffer.c | 2 +-
kernel/trace/trace.c | 24 +++---
kernel/trace/trace_event_types.h | 165 +++++++++++++++++++++++++++++++++++
kernel/trace/trace_events.c | 12 ++-
kernel/trace/trace_events_stage_2.h | 53 +-----------
kernel/trace/trace_export.c | 81 +++++++++++++++++
kernel/trace/trace_format.h | 55 ++++++++++++
kernel/trace/trace_sysprof.c | 2 +-
10 files changed, 329 insertions(+), 76 deletions(-)
--
next reply other threads:[~2009-03-06 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 3:18 Steven Rostedt [this message]
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 ` [tip:tracing/ftrace] tracing, power-trace: make it build even if the power-tracer is turned off 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=20090306031857.686507907@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 \
/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