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>,
Roel Kluin <roel.kluin@gmail.com>, Pekka Paalanen <pq@iki.fi>
Subject: [PATCH 0/3] ftrace: important updates
Date: Tue, 06 Jan 2009 17:33:37 -0500 [thread overview]
Message-ID: <20090106223337.677427397@goodmis.org> (raw)
Ingo,
The first patch is a critical fix that needs to get into 2.6.29.
The next patch is a rename of tracing_on to writing_enabled since
tracing_on is confusing, and the file enables or disables writes.
The last patch is a fix to tip that prevents a memory leak.
-- Steve
The following patches are in:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
branch: tip/devel
Frederic Weisbecker (1):
tracing/ftrace: fix a memory leak in stat tracing
Steven Rostedt (2):
ftrace: convert unsigned index to signed
ring-buffer: rename debugfs file tracing_on to writing_enabled
----
kernel/trace/ftrace.c | 4 ++--
kernel/trace/ring_buffer.c | 5 +++--
kernel/trace/trace_stat.c | 39 +++++++++++++++------------------------
3 files changed, 20 insertions(+), 28 deletions(-)
--
next reply other threads:[~2009-01-06 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 22:33 Steven Rostedt [this message]
2009-01-06 22:33 ` [PATCH 1/3] ftrace: convert unsigned index to signed Steven Rostedt
2009-01-06 22:50 ` Andrew Morton
2009-01-07 2:42 ` Steven Rostedt
2009-01-06 22:33 ` [PATCH 2/3] ring-buffer: rename debugfs file tracing_on to writing_enabled Steven Rostedt
2009-01-06 22:47 ` Andrew Morton
2009-01-07 2:52 ` Steven Rostedt
2009-01-06 22:33 ` [PATCH 3/3] tracing/ftrace: fix a memory leak in stat tracing Steven Rostedt
2009-01-06 22:51 ` Andrew Morton
2009-01-07 2:53 ` 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=20090106223337.677427397@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 \
--cc=pq@iki.fi \
--cc=roel.kluin@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.