)]}'
{
  "commit": "e277a1aaa97abdc1b0a0b8a8c062e29220b00440",
  "tree": "9ff0abc93858f4e519be55c2f594114000324961",
  "parents": [
    "cd05a1f818073a623455a58e756c5b419fc98db9"
  ],
  "author": {
    "name": "Sergei Shtylyov",
    "email": "sshtylyov@ru.mvista.com",
    "time": "Sat Mar 17 21:57:24 2007 +0100"
  },
  "committer": {
    "name": "Bartlomiej Zolnierkiewicz",
    "email": "bzolnier@gmail.com",
    "time": "Sat Mar 17 21:57:24 2007 +0100"
  },
  "message": "cmd64x: fix recovery time calculation (take 3)\n\nThe driver wrongly takes the address setup time into account when calculating\nthe PIO recovery time -- this leads to slight overclocking of the PIO modes 0\nand 1 (so, the prayers failed to help, as usual :-).  Rework the code to be\ncalculating recovery clock count as a difference between the total cycle count\nand the active count (we don\u0027t need to calculate the recovery time itself since\nit\u0027s not specified for the PIO modes 0 to 2, and for modes 3 and 4 this formula\ngives enough recovery time anyway in the chip\u0027s supported PCI frequency range).\n\nThis patch has been inspired by reading the datasheets and looking at what the\nlibata driver does; it has been compile-tested only (as usual :-) but anyway,\nthe new code gives the same or longer recovery times than the old one...\n\nSigned-off-by: Sergei Shtylyov \u003csshtylyov@ru.mvista.com\u003e\nSigned-off-by: Bartlomiej Zolnierkiewicz \u003cbzolnier@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b0d4825c56a9c45040dc062d05b185b2358869cd",
      "old_mode": 33188,
      "old_path": "drivers/ide/pci/cmd64x.c",
      "new_id": "561197f7b5bb92de6ae208d138cefaf6f9755082",
      "new_mode": 33188,
      "new_path": "drivers/ide/pci/cmd64x.c"
    }
  ]
}