linux-kernel - Re: [PATCH 0/4][GIT PULL] tracing: updates and fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100311124027.GF31354@elte.hu>
Date:	Thu, 11 Mar 2010 13:40:28 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 0/4][GIT PULL] tracing: updates and fixes


* Steven Rostedt <rostedt@...dmis.org> wrote:

> Ingo,
> 
> Please pull the latest tip/tracing/core tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/core
> 
> 
> Arnaldo Carvalho de Melo (1):
>       tracing: Update the comm field in the right variable in update_max_tr
> 
> Steven Rostedt (2):
>       function-graph: Fix unused reference to ftrace_set_func()
>       function-graph: Use comment notation for func names of dangling '}'
> 
> Tim Bird (1):
>       function-graph: Add tracing_thresh support to function_graph tracer
> 
> ----
>  kernel/trace/ftrace.c                |    6 ++----
>  kernel/trace/trace.c                 |   24 ++++++++++++++++++++----
>  kernel/trace/trace.h                 |    3 ++-
>  kernel/trace/trace_functions_graph.c |   27 ++++++++++++++++++++++++---
>  4 files changed, 48 insertions(+), 12 deletions(-)

Pulled, thanks Steve!

	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/