trace-cmd: Remove duplicate search for ftrace event in blktrace hack

The first try of the blktrace hack, I searched for a ftrace event.
But then I found that TRACE_BLK is not the same on all kernels so I
did a progressive search for a ftrace event to find where TRACE_BLK may
be.

The linear search was left over from the first attempt and no longer
needed.

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

1 files changed, 0 insertions, 10 deletions

diff --git a/trace-blk-hack.c b/trace-blk-hack.c
index 29c3c74..bdc9d13 100644
--- a/trace-blk-hack.c
+++ b/trace-blk-hack.c
@@ -53,7 +53,6 @@ int tracecmd_blk_hack(struct tracecmd_input *handle)
         int id;
         int l;
         int r;
-        int i;
 
         pevent = tracecmd_get_pevent(handle);
 
@@ -126,15 +125,6 @@ int tracecmd_blk_hack(struct tracecmd_input *handle)
          * to not write over the ftrace data.
          */
 
-        /* search for a ftrace event */
-        for (i = 0; i < 13; i++) {
-                event = pevent_find_event(pevent, i);
-                if (event)
-                        break;
-        }
-        if (!event)
-                goto fail;
-
         /* Make sure the common fields exist */
         field = pevent_find_common_field(event, "common_type");
         if (!field || field->offset != 0 || field->size != 2)