)]}'
{
  "commit": "6a6b97d360702b98c02c7fca4c4e088dcf3a2985",
  "tree": "6b0d6a504c11bbea7096706065c31bd12e7d7e78",
  "parents": [
    "58e20d8d344b0ee083febb18c2b021d2427e56ca"
  ],
  "author": {
    "name": "Tejun Heo",
    "email": "tj@kernel.org",
    "time": "Thu Nov 13 10:04:46 2008 +0900"
  },
  "committer": {
    "name": "Jeff Garzik",
    "email": "jgarzik@redhat.com",
    "time": "Fri Nov 14 18:51:57 2008 -0500"
  },
  "message": "libata: improve phantom device detection\n\nCurrently libata uses four methods to detect device presence.\n\n1. PHY status if available.\n2. TF register R/W test (only promotes presence, never demotes)\n3. device signature after reset\n4. IDENTIFY failure detection in SFF state machine\n\nCombination of the above works well in most cases but recently there\nhave been a few reports where a phantom device causes unnecessary\ndelay during probe.  In both cases, PHY status wasn\u0027t available.  In\none case, it passed #2 and #3 and failed IDENTIFY with ATA_ERR which\ndidn\u0027t qualify as #4.  The other failed #2 but as it passed #3 and #4,\nit still caused failure.\n\nIn both cases, phantom device reported diagnostic failure, so these\ncases can be safely worked around by considering any !ATA_DRQ IDENTIFY\nfailure as NODEV_HINT if diagnostic failure is set.\n\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\nSigned-off-by: Jeff Garzik \u003cjgarzik@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4b47394863279606dc7427d79789bdc8c8485d99",
      "old_mode": 33188,
      "old_path": "drivers/ata/libata-sff.c",
      "new_id": "9033d164c4ece13f876777fd7fbb549e4c27456b",
      "new_mode": 33188,
      "new_path": "drivers/ata/libata-sff.c"
    }
  ]
}