mirror of https://lore.kernel.org/lkml/
 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>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 00/10] ftrace: various updates
Date: Sat, 8 Nov 2008 09:42:27 +0100	[thread overview]
Message-ID: <20081108084226.GA18215@elte.hu> (raw)
In-Reply-To: <20081108034605.289816911@goodmis.org>


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

> Ingo,
> 
> The following patches are in:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> 
>     branch: tip/devel
> 
> 
> Matt Fleming (1):
>       ftrace: Align __mcount_loc sections
> 
> Steven Rostedt (9):
>       ftrace: fix set_ftrace_filter
>       ftrace: fix boot trace sched startup
>       ftrace: fix sched_switch API
>       ftrace: irqsoff tracer incorrect reset
>       ftrace: enable trace_printk by default
>       ftrace: remove ctrl_update method
>       ftrace: remove trace array ctrl
>       ftrace: force pass of preemptoff selftest
>       ftrace: display start of CPU buffer in trace output
> 
> ----
>  kernel/trace/ftrace.c             |    3 +
>  kernel/trace/trace.c              |   43 +++++++++++--------
>  kernel/trace/trace.h              |    8 ++-
>  kernel/trace/trace_boot.c         |   22 ++++------
>  kernel/trace/trace_functions.c    |   15 +------
>  kernel/trace/trace_irqsoff.c      |   19 +--------
>  kernel/trace/trace_mmiotrace.c    |   22 ++++------
>  kernel/trace/trace_nop.c          |   16 +------
>  kernel/trace/trace_sched_switch.c |   77 ++++++++++++++++++++++++----------
>  kernel/trace/trace_sched_wakeup.c |   21 ++--------
>  kernel/trace/trace_selftest.c     |   82 +++++++++++++++++++++++-------------
>  kernel/trace/trace_sysprof.c      |   16 +------
>  scripts/recordmcount.pl           |    4 ++
>  13 files changed, 172 insertions(+), 176 deletions(-)

pulled into tip/tracing/ftrace, thanks Steve!

	Ingo

      parent reply	other threads:[~2008-11-08  8:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-08  3:46 Steven Rostedt
2008-11-08  3:46 ` [PATCH 01/10] ftrace: fix set_ftrace_filter Steven Rostedt
2008-11-08  3:46 ` [PATCH 02/10] ftrace: fix boot trace sched startup Steven Rostedt
2008-11-08  4:12   ` Frédéric Weisbecker
2008-11-08 12:17     ` Steven Rostedt
2008-11-08  3:46 ` [PATCH 03/10] ftrace: fix sched_switch API Steven Rostedt
2008-11-08  4:20   ` Frédéric Weisbecker
2008-11-08  3:46 ` [PATCH 04/10] ftrace: irqsoff tracer incorrect reset Steven Rostedt
2008-11-08  3:46 ` [PATCH 05/10] ftrace: enable trace_printk by default Steven Rostedt
2008-11-08  3:46 ` [PATCH 06/10] ftrace: remove ctrl_update method Steven Rostedt
2008-11-08  3:46 ` [PATCH 07/10] ftrace: remove trace array ctrl Steven Rostedt
2008-11-08  3:46 ` [PATCH 08/10] ftrace: Align __mcount_loc sections Steven Rostedt
2008-11-08  3:55   ` Steven Rostedt
2008-11-08  3:46 ` [PATCH 09/10] ftrace: force pass of preemptoff selftest Steven Rostedt
2008-11-08  3:46 ` [PATCH 10/10] ftrace: display start of CPU buffer in trace output Steven Rostedt
2008-11-08  8:42 ` 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=20081108084226.GA18215@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®