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 00/10] [GIT PULL] tracing: various fixes
Date: Fri, 11 Nov 2011 09:33:39 +0100 [thread overview]
Message-ID: <20111111083339.GD14347@elte.hu> (raw)
In-Reply-To: <20111108012939.372220547@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-trace.git
> tip/perf/core
>
> Head SHA1: 7e9a49ef542610609144d1afcd516dc3fafac4d6
>
>
> Gleb Natapov (1):
> jump_label: jump_label_inc may return before the code is patched
>
> Ilya Dryomov (1):
> tracing: fix event_subsystem ref counting
>
> Jiri Olsa (1):
> tracing/latency: Fix header output for latency tracers
>
> Li Zefan (2):
> tracing: Restore system filter behavior
> tracing: update Documentation on max preds limit
>
> Steven Rostedt (5):
> tracing: Add boiler plate for subsystem filter
> lockdep: Show subclass in pretty print of lockdep output
> ftrace: Remove force undef config value left for testing
> perf: Fix parsing of __print_flags() in TP_printk()
> ftrace: Fix hash record accounting bug
>
> ----
> Documentation/trace/events.txt | 2 --
> include/linux/ftrace_event.h | 2 ++
> kernel/jump_label.c | 3 ++-
> kernel/lockdep.c | 30 +++++++++++++-----------------
> kernel/trace/ftrace.c | 5 +++--
> kernel/trace/trace.c | 15 +++++++++++++++
> kernel/trace/trace.h | 1 +
> kernel/trace/trace_events.c | 1 -
> kernel/trace/trace_events_filter.c | 33 +++++++++++++++++++++++++--------
> kernel/trace/trace_irqsoff.c | 13 ++++++++++++-
> kernel/trace/trace_sched_wakeup.c | 13 ++++++++++++-
> tools/perf/util/trace-event-parse.c | 2 ++
> 12 files changed, 87 insertions(+), 33 deletions(-)
Pulled, thanks a lot Steve!
Ingo
next prev parent reply other threads:[~2011-11-11 8:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 1:29 [PATCH 00/10] [GIT PULL] tracing: various fixes Steven Rostedt
2011-11-08 1:29 ` [PATCH 01/10] tracing: fix event_subsystem ref counting Steven Rostedt
2011-11-08 1:29 ` [PATCH 02/10] tracing: Restore system filter behavior Steven Rostedt
2011-11-08 1:29 ` [PATCH 03/10] tracing: Add boiler plate for subsystem filter Steven Rostedt
2011-11-08 1:29 ` [PATCH 04/10] tracing: update Documentation on max preds limit Steven Rostedt
2011-11-08 1:29 ` [PATCH 05/10] lockdep: Show subclass in pretty print of lockdep output Steven Rostedt
2011-11-08 1:29 ` [PATCH 06/10] ftrace: Remove force undef config value left for testing Steven Rostedt
2011-11-08 1:29 ` [PATCH 07/10] jump_label: jump_label_inc may return before the code is patched Steven Rostedt
2011-11-08 1:29 ` [PATCH 08/10] perf: Fix parsing of __print_flags() in TP_printk() Steven Rostedt
2011-11-08 1:29 ` [PATCH 09/10] ftrace: Fix hash record accounting bug Steven Rostedt
2011-11-08 1:29 ` [PATCH 10/10] tracing/latency: Fix header output for latency tracers Steven Rostedt
2011-11-11 8:33 ` Ingo Molnar [this message]
2011-11-29 21:33 ` [PATCH 00/10] [GIT PULL] tracing: various fixes Steven Rostedt
2011-12-03 9:20 ` Ingo Molnar
2011-12-05 0:31 ` Steven Rostedt
2011-12-05 9:47 ` 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=20111111083339.GD14347@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