)]}'
{
  "commit": "97e45dd4388caaf3a67ec3578df944c9a05b0619",
  "tree": "75e3502a1bf60401006361f4452e55ef2fac91b6",
  "parents": [
    "3eaebb67af70c14885e7e8990a39605a4b42da4b"
  ],
  "author": {
    "name": "Eunchan Kim",
    "email": "eunchan@google.com",
    "time": "Fri Sep 13 13:17:35 2019 -0700"
  },
  "committer": {
    "name": "Eunchan Kim",
    "email": "eunchan@google.com",
    "time": "Fri Sep 13 14:05:30 2019 -0700"
  },
  "message": "[prim/arbiter] Keep current request until acked\n\nIf downstream isn\u0027t ready (arb_ready \u003d 0), then if higher priority\nrequest comes later but before ready, it outtakes previous request,\nwhich results in the arb_data change.\n\nIt doesn\u0027t harm as the data supposes to be used when valid \u0026 ready. It,\nhowever, looks bad on the crossbar. inside `tlul_socket_m1` it could\nhappen that the downstream request write data or address could be\nchanged without notice, and it violates TL-UL spec.\n\nThis is related to #152\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2336300c5e85a452b94074aa635f9f2a48476a68",
      "old_mode": 33188,
      "old_path": "hw/ip/prim/rtl/prim_arbiter.sv",
      "new_id": "c9e7bd05c97450e68891aafb62c7be27bbf093bf",
      "new_mode": 33188,
      "new_path": "hw/ip/prim/rtl/prim_arbiter.sv"
    }
  ]
}