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>
Subject: Re: [PATCH v2 0/5] [GIT PULL] ftrace,tracing/events rebase updates.
Date: Fri, 17 Apr 2009 17:11:35 +0200	[thread overview]
Message-ID: <20090417151135.GG23493@elte.hu> (raw)
In-Reply-To: <20090417144055.857407604@goodmis.org>


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

> Ingo,
> 
> I have already sent these patches once to you. This version updates the
> change logs to put the impact lines at the end. It also folds in
> you delay.h missing header fix, and adds my fix to the event tests.
> The two updates are both done to tracing/events: add startup tests for events
> 
> The rest of the patches should be identical.
> 
> 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
> 
> 
> Avadh Patel (1):
>       tracing: add saved_cmdlines file to show cached task comms
> 
> Steven Rostedt (4):
>       ftrace: use module notifier for function tracer
>       tracing/events: add startup tests for events
>       tracing/events/ring-buffer: expose format of ring buffer headers to users
>       tracing/events: perform function tracing in event selftests
> 
> ----
>  include/linux/ftrace.h      |    7 -
>  include/linux/module.h      |    4 +
>  include/linux/ring_buffer.h |    5 +
>  kernel/module.c             |   19 +--
>  kernel/trace/ftrace.c       |   90 ++++++++++----
>  kernel/trace/ring_buffer.c  |   44 +++++++
>  kernel/trace/trace.c        |   53 ++++++++
>  kernel/trace/trace_events.c |  282 +++++++++++++++++++++++++++++++++++++++++++
>  8 files changed, 459 insertions(+), 45 deletions(-)

Pulled, thanks a lot Steve!

Will let you know if there's any further self-test failures.

	Ingo

  parent reply	other threads:[~2009-04-17 15:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 14:40 [PATCH v2 0/5] [GIT PULL] ftrace,tracing/events rebase updates Steven Rostedt
2009-04-17 14:40 ` [PATCH v2 1/5] ftrace: use module notifier for function tracer Steven Rostedt
2009-04-17 14:40 ` [PATCH v2 2/5] tracing/events: add startup tests for events Steven Rostedt
2009-04-17 14:40 ` [PATCH v2 3/5] tracing/events/ring-buffer: expose format of ring buffer headers to users Steven Rostedt
2009-04-17 14:40 ` [PATCH v2 4/5] tracing: add saved_cmdlines file to show cached task comms Steven Rostedt
2009-04-17 14:41 ` [PATCH v2 5/5] tracing/events: perform function tracing in event selftests Steven Rostedt
2009-04-17 15:11 ` Ingo Molnar [this message]
2009-04-17 15:13   ` [PATCH v2 0/5] [GIT PULL] ftrace,tracing/events rebase updates Ingo Molnar
2009-04-28 11:12     ` BUG: Function graph tracer hang Ingo Molnar
2009-04-28 20:32       ` Frederic Weisbecker
2009-04-28 20:47         ` Steven Rostedt
2009-04-29 10:40           ` Ingo Molnar
2009-04-29 12:24             ` Steven Rostedt
2009-05-03  9:02               ` 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=20090417151135.GG23493@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --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