)]}'
{
  "commit": "50e7f4ba0d20fc23c93b33675d7ea8e2e84da557",
  "tree": "4da5b0703e8a31ab78e95de925816796d4f3c0a1",
  "parents": [
    "41450166d2220a7884e4f0cbbd5691ec2d648baf"
  ],
  "author": {
    "name": "Andrew Jeffery",
    "email": "andrew@codeconstruct.com.au",
    "time": "Fri May 10 17:06:26 2024 +0930"
  },
  "committer": {
    "name": "Hao Jiang",
    "email": "jianghao@google.com",
    "time": "Tue Jul 07 15:47:18 2026 -0700"
  },
  "message": "NVMeDevice: Remove redundant start\n\nThe final act of starting the underlying NVMeMiIntf instance in\nNVMeDevice::finalize() is redundant. The contract of\nMctpEndpoint::subscribe() is that at least one of the callbacks will\nbe invoked at least once, to ensure visibility of the current endpoint\nstate. As such, if the endpoint is in the \u0027Available\u0027 state then\nNVMeDevice::available() will be invoked, which will in-turn invoke\nNVMeMiIntf::start(). Removal of the redundant call also removes the\ninitiation of one endpoint recovery request in the event that\nthat the endpoint is \u0027Degraded\u0027 at the time of the call to\nNVMeDevice::finalize().\n\nIt\u0027s not an error to invoke NVMeMiIntf::start() multiple times, so this\nhasn\u0027t been a concern, but it is unnecessary.\n\nChange-Id: Id2c2e5af864a2fde64205b62518df68d82783796\nSigned-off-by: Andrew Jeffery \u003candrew@codeconstruct.com.au\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "516a982274879edebf906e9e520ce5838f5b45f3",
      "old_mode": 33188,
      "old_path": "src/NVMeDevice.cpp",
      "new_id": "8a1307325df302d7b82b60da0352ac3e0a7f7f15",
      "new_mode": 33188,
      "new_path": "src/NVMeDevice.cpp"
    }
  ]
}