[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140605151540.672365024@goodmis.org>
Date: Thu, 05 Jun 2014 11:15:40 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: linux-kernel@...r.kernel.org
Cc: Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: [for-next][PATCH 0/5] tracing: More stuff for this merge window
I know the merge window has opened early (strange), but I'm still
sorting out patches to get into 3.16 before I do any pushes.
I also just discovered that I'm not getting emails from Fengguang Wu's
kbuild bot tests. I haven't been since March. All this time I thought
I was good enough not to trigger those bugs, but I was naive. I'm still
working the issue with Fengguang, but from my SMTP error message, I had:
Sender address rejected: need fully-qualified address; from=<kbuild@bee>
That "kbuild@bee" seems to be causing it to be rejected. I wonder
how many others are not getting these emails.
Anyway, I'm pushing this out because they passed my tests. Now I
need to look at all the error reports that Fengguang's test reported
and fix them up (he gave me a link to where reports are).
Enjoy.
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 64b8e48a72f45eedfdddfc62c25691d6c96ac919
Minchan Kim (1)
tracing: Print max callstack on stacktrace bug
Petr Mladek (1)
ftrace/x86: Call text_ip_addr() instead of the duplicated code
Steven Rostedt (Red Hat) (2)
tracing: Remove unused variable in trace_benchmark
tracing: Add __get_dynamic_array_len() macro for trace events
Yoshihiro YUNOMAE (1)
tracing: Eliminate double free on failure of allocation on boot up
----
arch/x86/kernel/ftrace.c | 11 +----------
include/trace/ftrace.h | 11 ++++++++++-
kernel/trace/trace.c | 4 ----
kernel/trace/trace_benchmark.c | 1 -
kernel/trace/trace_stack.c | 34 ++++++++++++++++++++++++++++++----
5 files changed, 41 insertions(+), 20 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists