)]}'
{
  "commit": "cab1da59c2ff3bf08d0a7becf9b51e43a724a85c",
  "tree": "0c6fc6e838320b24f91fb5778be6f88c40e5197d",
  "parents": [
    "7491e0e4096f426de4a47fa241442c84e63c5a64"
  ],
  "author": {
    "name": "Minwoo Im",
    "email": "minwoo.im@samsung.com",
    "time": "Tue Apr 18 09:26:21 2023 +0900"
  },
  "committer": {
    "name": "Klaus Jensen",
    "email": "k.jensen@samsung.com",
    "time": "Wed Jun 28 11:13:42 2023 +0200"
  },
  "message": "hw/nvme: consider COPY command in nvme_aio_err\n\nIf we don\u0027t have NVME_CMD_COPY consideration in the switch statement in\nnvme_aio_err(), it will go to have NVME_INTERNAL_DEV_ERROR and\n`req-\u003estatus` will be ovewritten to it.  During the aio context, it\nmight set the NVMe status field like NVME_CMD_SIZE_LIMIT, but it\u0027s\noverwritten in the nvme_aio_err().\n\nAdd consideration for the NVME_CMD_COPY not to overwrite the status at\nthe end of the function.\n\nSigned-off-by: Minwoo Im \u003cminwoo.im@samsung.com\u003e\nReviewed-by: Klaus Jensen \u003ck.jensen@samsung.com\u003e\nSigned-off-by: Klaus Jensen \u003ck.jensen@samsung.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "020f37a780e0e628862a7e705dd49cef69e319f0",
      "old_mode": 33188,
      "old_path": "hw/nvme/ctrl.c",
      "new_id": "e031c2250a84f486a8fc1645d27ae6adafc2bf4a",
      "new_mode": 33188,
      "new_path": "hw/nvme/ctrl.c"
    }
  ]
}