public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [PATCH 0/7] [GIT PULL] tip/tracing/ftrace
Date: Fri, 20 Mar 2009 10:15:17 +0100	[thread overview]
Message-ID: <20090320091517.GD16021@elte.hu> (raw)
In-Reply-To: <20090319200122.512803803@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
> 
> 
> Lai Jiangshan (1):
>       ftrace: protect running nmi (V3)
> 
> Steven Rostedt (6):
>       tracing: give easy way to clear trace buffer
>       function-graph: consolidate prologues for output
>       tracing: make print_(b)printk_msg_only global
>       function-graph: calculate function depth within function graph tracer
>       tracing: remove recording function depth from trace_printk
>       function-graph: show binary events as comments
> 
> ----
>  arch/x86/kernel/ftrace.c             |   63 ++++++----
>  kernel/trace/trace.c                 |   85 ++++++-------
>  kernel/trace/trace.h                 |    6 +-
>  kernel/trace/trace_event_types.h     |    2 -
>  kernel/trace/trace_functions_graph.c |  219 +++++++++++++++++++---------------
>  kernel/trace/trace_mmiotrace.c       |    2 +-
>  kernel/trace/trace_output.c          |   32 +++++
>  kernel/trace/trace_output.h          |    5 +
>  kernel/trace/trace_printk.c          |    8 +-
>  9 files changed, 243 insertions(+), 179 deletions(-)

Pulled, thanks Steve!

	Ingo

  parent reply	other threads:[~2009-03-20  9:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 20:01 [PATCH 0/7] [GIT PULL] tip/tracing/ftrace Steven Rostedt
2009-03-19 20:01 ` [PATCH 1/7] tracing: give easy way to clear trace buffer Steven Rostedt
2009-03-19 20:26   ` Frederic Weisbecker
2009-03-19 23:52     ` Steven Rostedt
2009-03-19 20:01 ` [PATCH 2/7] ftrace: protect running nmi (V3) Steven Rostedt
2009-03-19 20:01 ` [PATCH 3/7] function-graph: consolidate prologues for output Steven Rostedt
2009-03-19 20:01 ` [PATCH 4/7] tracing: make print_(b)printk_msg_only global Steven Rostedt
2009-03-19 20:01 ` [PATCH 5/7] function-graph: calculate function depth within function graph tracer Steven Rostedt
2009-03-19 20:01 ` [PATCH 6/7] tracing: remove recording function depth from trace_printk Steven Rostedt
2009-03-19 20:01 ` [PATCH 7/7] function-graph: show binary events as comments Steven Rostedt
2009-03-19 20:52   ` Frederic Weisbecker
2009-03-20  9:15 ` Ingo Molnar [this message]
2009-03-20 10:14   ` [PATCH 0/7] [GIT PULL] tip/tracing/ftrace Ingo Molnar
2009-03-20 13:56     ` Frederic Weisbecker
2009-03-20 16:02     ` 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=20090320091517.GD16021@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=laijs@cn.fujitsu.com \
    --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