)]}'
{
  "commit": "76e3a19d0691bbfcc559ce77ab3004818fab8f22",
  "tree": "6013a3ec01ea3f269280740346b98875c35a5478",
  "parents": [
    "c2f9e49f9bbfa2e111ab1e1628b96b560bae7cec"
  ],
  "author": {
    "name": "Martin Peschke",
    "email": "mpeschke@linux.vnet.ibm.com",
    "time": "Fri Jan 30 15:46:23 2009 +0100"
  },
  "committer": {
    "name": "James Bottomley",
    "email": "James.Bottomley@HansenPartnership.com",
    "time": "Tue Feb 10 11:15:17 2009 -0500"
  },
  "message": "[SCSI] sg: fix device number in blktrace data\n\nHi,\n\nwe have run into an issue with blktrace being started for sg devices.\nPlease apply.\n\nThanks,\nMartin\n\nFrom: Martin Peschke \u003cmpeschke@linux.vnet.ibm.com\u003e\n\nThe device number denoting a generic SCSI devices (sg) in a blktrace\ntrace is broken; major and minor are always 0. It looks like\nsdp-\u003edevice-\u003esdev_gendev.devt is not initialized properly.\nThe fix below uses other data to make up a valid device number,\nsimilar to the way an sg device number is generated for sysfs output.\n\nReported-by: Stefan Raspl \u003craspl@linux.vnet.ibm.com\u003e\nSigned-off-by: Martin Peschke \u003cmpeschke@linux.vnet.ibm.com\u003e\nAcked-by: Douglas Gilbert \u003cdgilbert@interlog.com\u003e\nSigned-off-by: James Bottomley \u003cJames.Bottomley@HansenPartnership.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8f0bd3f7a59fdbc9b8c50ab69904d388b4ce24c5",
      "old_mode": 33188,
      "old_path": "drivers/scsi/sg.c",
      "new_id": "516925d8b570c3fab05d5d1b0a6b729e0ebce395",
      "new_mode": 33188,
      "new_path": "drivers/scsi/sg.c"
    }
  ]
}