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-3.11][PATCH 0/4] tracing
Date: Sat, 03 Aug 2013 08:49:26 -0400 [thread overview]
Message-ID: <20130803124926.157378122@goodmis.org> (raw)
Hopefully this is the last of the fixes for 3.11. Famous last words.
These are some minor bug fixes, but still should be in 3.11 and stable.
-- Steve
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 9457158bbc0ee04ecef76862d73eecd8076e9c7b
Alexander Z Lam (2):
tracing: Make TRACE_ITER_STOP_ON_FREE stop the correct buffer
tracing: Fix reset of time stamps during trace_clock changes
Andrew Vagin (1):
tracing: Fix fields of struct trace_iterator that are zeroed by mistake
Dhaval Giani (1):
tracing: Fix trace_dump_stack() proto when CONFIG_TRACING is not set
----
include/linux/ftrace_event.h | 10 ++++++----
include/linux/kernel.h | 2 +-
kernel/trace/trace.c | 27 ++++++++++++++-------------
3 files changed, 21 insertions(+), 18 deletions(-)
next reply other threads:[~2013-08-03 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 12:49 Steven Rostedt [this message]
2013-08-03 12:49 ` [for-next-3.11][PATCH 1/4] tracing: Fix fields of struct trace_iterator that are zeroed by mistake Steven Rostedt
2013-08-03 12:49 ` [for-next-3.11][PATCH 2/4] tracing: Fix trace_dump_stack() proto when CONFIG_TRACING is not set Steven Rostedt
2013-08-03 12:49 ` [for-next-3.11][PATCH 3/4] tracing: Make TRACE_ITER_STOP_ON_FREE stop the correct buffer Steven Rostedt
2013-08-03 12:49 ` [for-next-3.11][PATCH 4/4] tracing: Fix reset of time stamps during trace_clock changes Steven Rostedt
2013-08-08 16:12 ` Steven Rostedt
2013-08-12 4:13 ` Greg Kroah-Hartman
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=20130803124926.157378122@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