)]}'
{
  "commit": "a4e7f25c408902677824f5edc3f6ad1e760241a3",
  "tree": "4ec278dde3bf09c6bc146cad0727a8d3e6ab4b63",
  "parents": [
    "e317e9c31cef31f960a5cfb3e3247047d39ae7a1"
  ],
  "author": {
    "name": "Nico Huber",
    "email": "nico.huber@secunet.com",
    "time": "Tue Sep 17 16:25:49 2019 +0200"
  },
  "committer": {
    "name": "Nico Huber",
    "email": "nico.h@gmx.de",
    "time": "Sat Oct 05 23:23:59 2019 +0000"
  },
  "message": "gma i2c: Increase timeout, again\n\nCan a timeout be long enough? We still face the same problem as in\n68f439d4f1 (gma i2c: Increase timeout to \u003e100ms). User reports have\nshown, that the 110ms still were not enough, 200ms would be but to\nbe safe this time, increase the timeout to 500ms. That may result\nin very long delays, but only if the hardware is even more broken\nthat what we encountered so far.\n\nChange-Id: Ia7b28f5a4ed1cd382a7ebfba5ce1ffe1b7a333a8\nSigned-off-by: Nico Huber \u003cnico.huber@secunet.com\u003e\nReviewed-on: https://review.coreboot.org/c/libgfxinit/+/35450\nTested-by: Nico Huber \u003cnico.h@gmx.de\u003e\nReviewed-by: Angel Pons \u003cth3fanbus@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3d4117425d6cb63a5a7468b8371e2af9b9106c7a",
      "old_mode": 33188,
      "old_path": "common/hw-gfx-gma-i2c.adb",
      "new_id": "a958e260fd5bd729d5802e60a7ca7d2349d2e7eb",
      "new_mode": 33188,
      "new_path": "common/hw-gfx-gma-i2c.adb"
    }
  ]
}