)]}'
{
  "commit": "4efc76bdbf9bfd2b8624c4dd52b9d8ffed176b31",
  "tree": "49be6ee8edf101521f45c72773bc73a6351f11c8",
  "parents": [
    "8b58ff832df9222e1fb3c58ae7f745f95569b55e"
  ],
  "author": {
    "name": "Johannes Berg",
    "email": "johannes.berg@intel.com",
    "time": "Thu Jun 10 10:56:20 2010 +0200"
  },
  "committer": {
    "name": "John W. Linville",
    "email": "linville@tuxdriver.com",
    "time": "Mon Jun 14 15:39:29 2010 -0400"
  },
  "message": "mac80211: bracket driver tracing\n\nCurrently, driver tracing is sometimes invoked\nafter and sometimes before the actual driver\ncallback. This is fine as long as the driver\nhas no tracing itself, but as soon as it does\nit gets confusing.\n\nTo make traces containing such information\neasier to read, introduce a return tracer in\nmac80211 that essentially brackets any driver\ntracing, and invoke the real trace before the\ndriver\u0027s callback, only showing the return\nvalue, if any, afterwards.\n\nSince tracing records the process, there\u0027s no\nproblem with overlapping calls if that should\nhappen.\n\nSigned-off-by: Johannes Berg \u003cjohannes.berg@intel.com\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a4fcbcc4f458ecbed3e7d2361d9b4744e99ffa9c",
      "old_mode": 33188,
      "old_path": "net/mac80211/driver-ops.h",
      "new_id": "965d64f685671377a4371b84f0c4fb4706f41087",
      "new_mode": 33188,
      "new_path": "net/mac80211/driver-ops.h"
    },
    {
      "type": "modify",
      "old_id": "6b90630151abb4a0dba8b573822b5b41c1035190",
      "old_mode": 33188,
      "old_path": "net/mac80211/driver-trace.h",
      "new_id": "06444ea67bc4b8bf8d488357b54a7efa0b30d56b",
      "new_mode": 33188,
      "new_path": "net/mac80211/driver-trace.h"
    }
  ]
}