[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090509042714.GE8007@elte.hu>
Date: Sat, 9 May 2009 06:27:14 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Li Zefan <lizf@...fujitsu.com>
Subject: Re: [PATCH 0/2] [GIT PULL] tracing: updates for tip
* Steven Rostedt <rostedt@...dmis.org> wrote:
> Ingo,
>
> The first patch fixes a uninitialized variable. What bothers me
> about this, is that gcc did not warn about it. My gcc warns about
> a ton of variables that might not being initialized, but missed
> one that actually is not!
>
> I wonder if it is only my version of gcc: 4.2.2
> :-/
>
> Please pull the latest tip/tracing/ftrace-1 tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/ftrace-1
>
>
> Steven Rostedt (2):
> tracing: initialize return value for __ftrace_set_clr_event
> tracing: add trace_set_clr_event to export event enabling function
>
> ----
> include/linux/ftrace_event.h | 2 ++
> kernel/trace/trace_events.c | 19 ++++++++++++++++++-
> 2 files changed, 20 insertions(+), 1 deletions(-)
Pulled, thanks Steve!
Note, the above branch gave conflicts in ring_buffer.c. But i pulled
at commit 4671c79 from your tree which gave the same diffstat:
Fast forward
include/linux/ftrace_event.h | 2 ++
kernel/trace/trace_events.c | 19 ++++++++++++++++++-
2 files changed, 20 insertions(+), 1 deletions(-)
Please double-check that i got the right bits. Thanks,
Ingo
--
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