)]}'
{
  "commit": "d2ee9cd2e2bdfa2e5817142d6f044697066d3977",
  "tree": "9e4dec9fd4c009b8ce12f3bd1529ef2b455d3cc1",
  "parents": [
    "c491bf1205485c83086bf4f2f26ca6598d48133a"
  ],
  "author": {
    "name": "Reinette Chatre",
    "email": "reinette.chatre@intel.com",
    "time": "Tue Apr 21 10:55:47 2009 -0700"
  },
  "committer": {
    "name": "John W. Linville",
    "email": "linville@tuxdriver.com",
    "time": "Tue Apr 21 16:43:34 2009 -0400"
  },
  "message": "iwlwifi: add debugging for TX path\n\nWhen debugging TX issues it is helpful to know the seq nr of the\nframe being transmitted. The seq nr is printed as part of ucode\u0027s\nlog informing us which frame is being processed. Having this information\nprinted in driver log makes it easy to match activities between driver\nand firmware.\n\nAlso make possible to print TX flags directly. These are already printed\nas part of entire TX command, but having it printed directly in cpu format\nmakes it easier to look at.\n\nSigned-off-by: Reinette Chatre \u003creinette.chatre@intel.com\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1f117a49c569422ae31a0d6f69a0fa2ea11a8f9b",
      "old_mode": 33188,
      "old_path": "drivers/net/wireless/iwlwifi/iwl-tx.c",
      "new_id": "8ef53e28176ff35993468aa12afcee70387ad2a6",
      "new_mode": 33188,
      "new_path": "drivers/net/wireless/iwlwifi/iwl-tx.c"
    },
    {
      "type": "modify",
      "old_id": "1299479f99dc4997d5b5f831bcd2a078c0aeb9e7",
      "old_mode": 33188,
      "old_path": "drivers/net/wireless/iwlwifi/iwl3945-base.c",
      "new_id": "acefc37212672048b36acf1ed3757c73276bfd38",
      "new_mode": 33188,
      "new_path": "drivers/net/wireless/iwlwifi/iwl3945-base.c"
    }
  ]
}