)]}'
{
  "commit": "b304d0441a4118fadd4c3f16e4dc600c271030b5",
  "tree": "ed477c965cf6eaf852f69f7dd855c0ea83f8e36d",
  "parents": [
    "2bd16212b8eb86f9574e78d6605a5ba9e9aa8c4e"
  ],
  "author": {
    "name": "Steven Rostedt",
    "email": "srostedt@redhat.com",
    "time": "Tue Sep 14 18:58:33 2010 -0400"
  },
  "committer": {
    "name": "Steven Rostedt",
    "email": "rostedt@goodmis.org",
    "time": "Tue Sep 14 20:18:07 2010 -0400"
  },
  "message": "tracing: Do not trace in irq when funcgraph-irq option is zero\n\nWhen the function graph tracer funcgraph-irq option is zero, disable\ntracing in IRQs. This makes the option have two effects.\n\n1) When reading the trace file, do not display the functions that\n   happen in interrupt context (when detected)\n\n2) [*new*] When recording a trace, skip those that are detected\n   to be in interrupt by the \u0027in_irq()\u0027 function\n\nNote, in_irq() is updated at irq_enter() and irq_exit(). There are\nstill functions that are recorded by the function graph tracer that\nis in interrupt context but outside the irq_enter/exit() routines.\n\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8674750a5ecec8497836d0e9cbe450f757ee8473",
      "old_mode": 33188,
      "old_path": "kernel/trace/trace_functions_graph.c",
      "new_id": "02c708ae0d420180d1125580820d9ff85cb3d94d",
      "new_mode": 33188,
      "new_path": "kernel/trace/trace_functions_graph.c"
    }
  ]
}