)]}'
{
  "commit": "78c89ba121221d9224a5747803d7fffe51cd6e44",
  "tree": "08f529d73a27513014a15c0a21dfa2d106a68368",
  "parents": [
    "5e6d2b9cfa3a6e7fe62fc0135bc1bd778f5db564"
  ],
  "author": {
    "name": "Steven Rostedt",
    "email": "srostedt@redhat.com",
    "time": "Tue Oct 05 23:22:19 2010 -0400"
  },
  "committer": {
    "name": "Steven Rostedt",
    "email": "rostedt@goodmis.org",
    "time": "Mon Oct 18 10:53:38 2010 -0400"
  },
  "message": "tracing: Remove parent recording in latency tracer graph options\n\nEven though the parent is recorded with the normal function tracing\nof the latency tracers (irqsoff and wakeup), the function graph\nrecording is bogus.\n\nThis is due to the function graph messing with the return stack.\nThe latency tracers pass in as the parent CALLER_ADDR0, which\nworks fine for plain function tracing. But this causes bogus output\nwith the graph tracer:\n\n 3)    \u003cidle\u003e-0    |  d.s3.  0.000 us    |  return_to_handler();\n 3)    \u003cidle\u003e-0    |  d.s3.  0.000 us    |  _raw_spin_unlock_irqrestore();\n 3)    \u003cidle\u003e-0    |  d.s3.  0.000 us    |  return_to_handler();\n 3)    \u003cidle\u003e-0    |  d.s3.  0.000 us    |  trace_hardirqs_on();\n\nThe \"return_to_handle()\" call is the trampoline of the\nfunction graph tracer, and is meaningless in this context.\n\nCc: Jiri Olsa \u003cjolsa@redhat.com\u003e\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6f8fe28acba11eaf1a585253fb57490537dca610",
      "old_mode": 33188,
      "old_path": "kernel/trace/trace_functions_graph.c",
      "new_id": "76b05980225cb79df8bfad7bb35cd64bd52bcaf2",
      "new_mode": 33188,
      "new_path": "kernel/trace/trace_functions_graph.c"
    }
  ]
}