diff options
| author | Peter Zijlstra <[email protected]> | 2017-10-11 09:45:29 +0200 |
|---|---|---|
| committer | Steven Rostedt (VMware) <[email protected]> | 2017-10-16 18:11:02 -0400 |
| commit | 8fd0fbbe8888f295eb34172a7e47bf7d3a0a4687 (patch) | |
| tree | 86e13d1e79b9c407f4d142f12ea43fc1b008f617 /lib/mpi/mpiutil.c | |
| parent | 136412474b77c14a26e018a7f2c1e5fcee700d3d (diff) | |
perf/ftrace: Revert ("perf/ftrace: Fix double traces of perf on ftrace:function")
Revert commit:
75e8387685f6 ("perf/ftrace: Fix double traces of perf on ftrace:function")
The reason I instantly stumbled on that patch is that it only addresses the
ftrace situation and doesn't mention the other _5_ places that use this
interface. It doesn't explain why those don't have the problem and if not, why
their solution doesn't work for ftrace.
It doesn't, but this is just putting more duct tape on.
Link: http://lkml.kernel.org/r/[email protected]
Cc: Zhou Chengming <[email protected]>
Cc: Jiri Olsa <[email protected]>
Cc: Ingo Molnar <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Signed-off-by: Steven Rostedt (VMware) <[email protected]>
Diffstat (limited to 'lib/mpi/mpiutil.c')
0 files changed, 0 insertions, 0 deletions