)]}'
{
  "commit": "75683fe7153c3817bb4fd4491e2a5913af6c463e",
  "tree": "5c7bb12e577a328b41df16d036c7060309493f44",
  "parents": [
    "39ce7128066f2ac5954bcda9f07f429f28166da3"
  ],
  "author": {
    "name": "Tejun Heo",
    "email": "htejun@gmail.com",
    "time": "Thu Jul 05 13:31:27 2007 +0900"
  },
  "committer": {
    "name": "Jeff Garzik",
    "email": "jeff@garzik.org",
    "time": "Tue Jul 10 21:30:33 2007 -0400"
  },
  "message": "libata: clean up horkage handling\n\nHorkage handling had the following problems.\n\n* dev-\u003ehorkage was positioned after ATA_DEVICE_CLEAR_OFFSET, so it was\n  cleared before the device is configured.  This broke\n  HORKAGE_DIAGNOSTIC.\n\n* Some used dev-\u003ehorkage while others called ata_device_blacklisted()\n  directly.  This was at best confusing.\n\nThis patch moves dev-\u003ehorkage right after dev-\u003eflags and set the field\naccording to the blacklist during device configuration.  All users\ntest against dev-\u003ehorkage.  ata_device_blacklisted() now has only one\nuser, make it static.  While at it, rename it to ata_dev_blacklisted()\nfor consistency.\n\nSigned-off-by: Tejun Heo \u003chtejun@gmail.com\u003e\nSigned-off-by: Jeff Garzik \u003cjeff@garzik.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a00e4ee58b73d07750bf114e69c7adecb5ee5932",
      "old_mode": 33188,
      "old_path": "drivers/ata/libata-core.c",
      "new_id": "66c8c8c377ab14a7e49b9d676e58bc346ca65e04",
      "new_mode": 33188,
      "new_path": "drivers/ata/libata-core.c"
    },
    {
      "type": "modify",
      "old_id": "0c8b6578bd596a1cffcab8ab6f6f81ab22e0b1ab",
      "old_mode": 33188,
      "old_path": "include/linux/libata.h",
      "new_id": "47cd2a1c554487b7ae6a028a085b1107c7090712",
      "new_mode": 33188,
      "new_path": "include/linux/libata.h"
    }
  ]
}