Re: [PATCH 0/3 v2] [GIT PULL][3.9] tracing: Fixes with flags and latency tracers

* Steven Rostedt wrote: > > Ingo, > > Here's take two of the last patch series I sent. The only difference > with this series is that I encapsulate the max_tr reference with > the #ifdef CONFIG_TRACER_MAX_TRACE. Other than that, it's the same. > > Here's the recap: > > The first patch fixes

Re: [PATCH 0/3 v2] [GIT PULL][3.9] tracing: Fixes with flags and latency tracers

* Steven Rostedt rost...@goodmis.org wrote: Ingo, Here's take two of the last patch series I sent. The only difference with this series is that I encapsulate the max_tr reference with the #ifdef CONFIG_TRACER_MAX_TRACE. Other than that, it's the same. Here's the recap: The first

[PATCH 0/3 v2] [GIT PULL][3.9] tracing: Fixes with flags and latency tracers

Ingo, Here's take two of the last patch series I sent. The only difference with this series is that I encapsulate the max_tr reference with the #ifdef CONFIG_TRACER_MAX_TRACE. Other than that, it's the same. Here's the recap: The first patch fixes a long standing bug where the changing of the

[PATCH 0/3 v2] [GIT PULL][3.9] tracing: Fixes with flags and latency tracers

Ingo, Here's take two of the last patch series I sent. The only difference with this series is that I encapsulate the max_tr reference with the #ifdef CONFIG_TRACER_MAX_TRACE. Other than that, it's the same. Here's the recap: The first patch fixes a long standing bug where the changing of the