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>
Subject: Re: [PATCH 0/7] [GIT PULL] tracing: updates
Date: Fri, 23 Jul 2010 09:12:37 +0200	[thread overview]
Message-ID: <20100723071237.GB23461@elte.hu> (raw)
In-Reply-To: <20100722202411.920807480@goodmis.org>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> 
> Ingo,
> 
> 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
> 
> 
> Dan Carpenter (1):
>       trace: strlen() return doesn't account for the NULL
> 
> David Daney (1):
>       tracing: Fix $mcount_regex for MIPS in recordmcount.pl
> 
> KOSAKI Motohiro (1):
>       tracing: Shrink max latency ringbuffer if unnecessary
> 
> Lai Jiangshan (1):
>       tracing: Reduce latency and remove percpu trace_seq
> 
> Li Zefan (1):
>       tracing: Allow to disable cmdline recording
> 
> Mike Frysinger (1):
>       tracing/documentation: Document dynamic ftracer internals
> 
> Richard Kennedy (1):
>       trace: Reorder struct ring_buffer_per_cpu to remove padding on 64bit
> 
> ----
>  Documentation/trace/ftrace-design.txt |  153 +++++++++++++++++++++++++++++++-
>  include/linux/ftrace.h                |    5 +
>  include/linux/ftrace_event.h          |   12 ++-
>  include/trace/ftrace.h                |   12 +--
>  kernel/trace/ring_buffer.c            |    2 +-
>  kernel/trace/trace.c                  |   46 ++++++++--
>  kernel/trace/trace.h                  |    4 +
>  kernel/trace/trace_events.c           |   30 ++++++-
>  kernel/trace/trace_irqsoff.c          |    3 +
>  kernel/trace/trace_output.c           |    3 -
>  kernel/trace/trace_sched_wakeup.c     |    2 +
>  scripts/recordmcount.pl               |    2 +-
>  12 files changed, 241 insertions(+), 33 deletions(-)

Pulled, thanks a lot Steve!

	Ingo

  parent reply	other threads:[~2010-07-23  7:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 20:24 [PATCH 0/7] [GIT PULL] tracing: updates Steven Rostedt
2010-07-22 20:24 ` [PATCH 1/7] tracing: Allow to disable cmdline recording Steven Rostedt
2010-07-22 20:24 ` [PATCH 2/7] trace: Reorder struct ring_buffer_per_cpu to remove padding on 64bit Steven Rostedt
2010-07-22 20:24 ` [PATCH 3/7] tracing: Reduce latency and remove percpu trace_seq Steven Rostedt
2010-07-22 20:24 ` [PATCH 4/7] tracing: Shrink max latency ringbuffer if unnecessary Steven Rostedt
2010-07-22 20:24 ` [PATCH 5/7] tracing/documentation: Document dynamic ftracer internals Steven Rostedt
2010-07-22 20:24 ` [PATCH 6/7] tracing: Fix $mcount_regex for MIPS in recordmcount.pl Steven Rostedt
2010-07-22 20:24 ` [PATCH 7/7] trace: strlen() return doesnt account for the NULL Steven Rostedt
2010-07-23  7:12 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-01  3:17 [PATCH 0/7] [GIT PULL] tracing: updates Steven Rostedt
2010-04-02 16:39 ` Ingo Molnar
2010-02-25 19:43 [PATCH 0/7][GIT " Steven Rostedt
2010-02-26  8:21 ` 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=20100723071237.GB23461@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.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