From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/3 v2] [GIT PULL][v3.0] tracing: various fixes
Date: Thu, 07 Jul 2011 16:57:56 -0400 [thread overview]
Message-ID: <20110707205755.992304506@goodmis.org> (raw)
Ingo,
I rebased the last two patches but only changed the change logs.
The first patch I rephrased the subject, the second patch I rewrote
the change log to something that explains things much better.
I also added a third patch that fixes a regression that was reported
to me earlier today.
Please pull the latest tip/perf/urgent-2 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/perf/urgent-2
Head SHA1: 43dd61c9a09bd413e837df829e6bfb42159be52a
Steven Rostedt (3):
tracing: Fix bug when reading system filters on module removal
tracing: Have "enable" file use refcounts like the "filter" file
ftrace: Fix regression of :mod:module function enabling
----
include/linux/ftrace.h | 3 +-
kernel/trace/ftrace.c | 12 +---
kernel/trace/trace.h | 1 +
kernel/trace/trace_events.c | 113 ++++++++++++++++++++++++++++++------
kernel/trace/trace_events_filter.c | 6 ++
kernel/trace/trace_functions.c | 3 +-
6 files changed, 109 insertions(+), 29 deletions(-)
next reply other threads:[~2011-07-07 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 20:57 Steven Rostedt [this message]
2011-07-07 20:57 ` [PATCH 1/3 v2] tracing: Fix bug when reading system filters on module removal Steven Rostedt
2011-07-07 20:57 ` [PATCH 2/3 v2] tracing: Have "enable" file use refcounts like the "filter" file Steven Rostedt
2011-07-07 20:57 ` [PATCH 3/3 v2] ftrace: Fix regression of :mod:module function enabling Steven Rostedt
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=20110707205755.992304506@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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