)]}'
{
  "commit": "d21e9daa63e009ce5b87bbcaa6d11ce48e07bbbe",
  "tree": "e09b0f6c6e6016ad0a425afe0a7e10b89c3138ac",
  "parents": [
    "22ed130719987d1081831dc1481160b216224ffd"
  ],
  "author": {
    "name": "Christof Schmitt",
    "email": "christof.schmitt@de.ibm.com",
    "time": "Wed Feb 17 11:18:54 2010 +0100"
  },
  "committer": {
    "name": "James Bottomley",
    "email": "James.Bottomley@suse.de",
    "time": "Wed Feb 17 17:46:27 2010 -0600"
  },
  "message": "[SCSI] zfcp: Dont use 0 to indicate invalid LUN in rec trace\n\n0 is a valid value for a LUN. It is slightly confusing to also see 0\nin the trace entries relating to adapter and port. Change this to use\n0xFFFFFFFFFFFFFFFF in the LUN field when the trace entry does not\nrelate to a LUN or unit.\n\nReviewed-by: Swen Schillig \u003cswen@vnet.ibm.com\u003e\nSigned-off-by: Christof Schmitt \u003cchristof.schmitt@de.ibm.com\u003e\nSigned-off-by: James Bottomley \u003cJames.Bottomley@suse.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "818b6ad935ad21243f7c2933a653ad3800c301d5",
      "old_mode": 33188,
      "old_path": "drivers/s390/scsi/zfcp_dbf.c",
      "new_id": "c8d68fec633455273319c081e919a29553f5927a",
      "new_mode": 33188,
      "new_path": "drivers/s390/scsi/zfcp_dbf.c"
    },
    {
      "type": "modify",
      "old_id": "e4b5317fe902a0cd4829ee338e089b66c858a640",
      "old_mode": 33188,
      "old_path": "drivers/s390/scsi/zfcp_dbf.h",
      "new_id": "ca841ee44c15c195bbdf41cd2477ef3823657f53",
      "new_mode": 33188,
      "new_path": "drivers/s390/scsi/zfcp_dbf.h"
    }
  ]
}
