)]}'
{
  "commit": "f2bf1f6f5f89d031245067512449fc889b2f4bb2",
  "tree": "3211ae100915962ccdc4ea7a4b521ddfe2697cad",
  "parents": [
    "5041caa4d5e6dae418963de0c8f8a83f35e35dcf"
  ],
  "author": {
    "name": "Steven Rostedt",
    "email": "srostedt@redhat.com",
    "time": "Wed Jun 06 19:50:40 2012 -0400"
  },
  "committer": {
    "name": "Steven Rostedt",
    "email": "rostedt@goodmis.org",
    "time": "Wed Jun 06 22:15:14 2012 -0400"
  },
  "message": "tracing: Have tracing_off() actually turn tracing off\n\nA recent update to have tracing_on/off() only affect the ftrace ring\nbuffers instead of all ring buffers had a cut and paste error.\nThe tracing_off() did the exact same thing as tracing_on() and\nwould not actually turn off tracing. Unfortunately, tracing_off()\nis more important to be working than tracing_on() as this is a key\ndevelopment tool, as it lets the developer turn off tracing as soon\nas a problem is discovered. It is also used by panic and oops code.\n\nThis bug also breaks the \u0027echo func:traceoff \u003e set_ftrace_filter\u0027\n\nCc: \u003cstable@vger.kernel.org\u003e # 3.4\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "68032c6177dbb84a28d0bc432773f841101c11b4",
      "old_mode": 33188,
      "old_path": "kernel/trace/trace.c",
      "new_id": "49249c28690dbb21b6914e2907b16af56e1094c9",
      "new_mode": 33188,
      "new_path": "kernel/trace/trace.c"
    }
  ]
}