From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/5] tracing: More updates for 3.13
Date: Wed, 06 Nov 2013 23:00:02 -0500 [thread overview]
Message-ID: <20131107040002.605895766@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 20b72e76c42bc4f0dd091f9faee542ea45ad6b5e
Cody P Schafer (1):
tracing: Open tracer when ftrace_dump_on_oops is used
Geyslan G. Bem (2):
tracing: Add helper function tracing_is_disabled()
tracing: Do not assign filp->private_data to freed memory
Steven Rostedt (1):
Merge branch 'trace/ftrace/core' into trace/for-next
Steven Rostedt (Red Hat) (2):
tracing: Remove unused function ftrace_off_permanent()
tracing: Do not use signed enums with unsigned long long in fgragh output
----
include/linux/kernel.h | 2 --
kernel/trace/trace.c | 31 ++++++++++++++++---------------
kernel/trace/trace.h | 3 +++
kernel/trace/trace_events.c | 9 ++++++++-
kernel/trace/trace_functions_graph.c | 22 +++++++++++-----------
5 files changed, 38 insertions(+), 29 deletions(-)
next reply other threads:[~2013-11-07 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 4:00 Steven Rostedt [this message]
2013-11-07 4:00 ` [for-next][PATCH 1/5] tracing: Open tracer when ftrace_dump_on_oops is used Steven Rostedt
2013-11-07 4:00 ` [for-next][PATCH 2/5] tracing: Add helper function tracing_is_disabled() Steven Rostedt
2013-11-07 4:00 ` [for-next][PATCH 3/5] tracing: Do not assign filp->private_data to freed memory Steven Rostedt
2013-11-07 4:00 ` [for-next][PATCH 4/5] tracing: Remove unused function ftrace_off_permanent() Steven Rostedt
2013-11-07 4:00 ` [for-next][PATCH 5/5] tracing: Do not use signed enums with unsigned long long in fgragh output 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=20131107040002.605895766@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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
Powered by JetHome