Re: [PATCH V2 -tip 3/4] Tracing/ftrace: Adapt mmiotrace to the new type of print_line

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Frédéric Weisbecker
Date: Tuesday, September 30, 2008 - 6:25 am

2008/9/30 Steven Rostedt <rostedt@goodmis.org>:

Strange, I can't see any case where print_trace_line could call the
ring_buffer_lock.
Hmm, I will see in your patch.

Ingo, I just saw one damage from the merging, trace_empty() returns
TRACE_TYPE_HANDLED. The type is wrong, it should return 1.
It's not urgent since the value is the same. Should I send a patch for
such a small error?

Thanks.
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH V2 -tip 3/4] Tracing/ftrace: Adapt mmiotrace to the ..., Frederic Weisbecker, (Mon Sep 29, 11:27 am)
Re: [PATCH V2 -tip 3/4] Tracing/ftrace: Adapt mmiotrace to ..., Frédéric Weisbecker, (Tue Sep 30, 5:39 am)
Re: [PATCH V2 -tip 3/4] Tracing/ftrace: Adapt mmiotrace to ..., Frédéric Weisbecker, (Tue Sep 30, 6:25 am)
Re: [PATCH V2 -tip 3/4] Tracing/ftrace: Adapt mmiotrace to ..., Frederic Weisbecker, (Tue Sep 30, 9:13 am)
Re: [PATCH V2 -tip 3/4] Tracing/ftrace: Adapt mmiotrace to ..., Frédéric Weisbecker, (Tue Sep 30, 9:16 am)