From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/3] [GIT PULL] update for tip/tracing/ftrace
Date: Tue, 17 Mar 2009 10:36:59 +0100 [thread overview]
Message-ID: <20090317093659.GC6477@elte.hu> (raw)
In-Reply-To: <20090317034820.400357912@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> 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
>
>
> Frederic Weisbecker (1):
> tracing/ftrace: fix the check on nopped sites
>
> Steven Rostedt (2):
> tracing: protect reader of cmdline output
> tracing: stop comm recording on tracing off
>
> ----
> kernel/trace/blktrace.c | 23 ++++++++++++++++++-----
> kernel/trace/ftrace.c | 2 +-
> kernel/trace/trace.c | 22 +++++++++++++---------
> kernel/trace/trace.h | 2 +-
> kernel/trace/trace_functions_graph.c | 12 ++++++------
> kernel/trace/trace_output.c | 18 ++++++++++++------
> 6 files changed, 51 insertions(+), 28 deletions(-)
Pulled, thanks Steve!
Ingo
prev parent reply other threads:[~2009-03-17 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 3:48 [PATCH 0/3] [GIT PULL] update for tip/tracing/ftrace Steven Rostedt
2009-03-17 3:48 ` [PATCH 1/3] tracing/ftrace: fix the check on nopped sites Steven Rostedt
2009-03-17 3:48 ` [PATCH 2/3] tracing: protect reader of cmdline output Steven Rostedt
2009-03-17 3:48 ` [PATCH 3/3] tracing: stop comm recording on tracing off Steven Rostedt
2009-03-17 9:36 ` 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=20090317093659.GC6477@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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