)]}'
{
  "commit": "bae5aca4c81a4e8449bb1ede46342b33aecf4e5a",
  "tree": "90c80e5c120cb107cd13ffac0a88875c397a6be6",
  "parents": [
    "da725bd4a67c5d65ab45631f6d26f61afa524fe1"
  ],
  "author": {
    "name": "Hao Jiang",
    "email": "jianghao@google.com",
    "time": "Fri Aug 14 21:30:19 2026 +0000"
  },
  "committer": {
    "name": "mdb:gbmc-git-owners",
    "email": "superproject-auto-update@invalid",
    "time": "Wed Aug 19 13:30:23 2026 -0700"
  },
  "message": "nvme: restore backward compatibility for mi_i2c without bus property\n\nFor NVMe devices configured with protocol \"mi_i2c\" and associated\nwith MCTP reactor configurations (isMctpReactorDevice), the \"Bus\"\nproperty is optional because endpoint discovery and routing are\nresolved dynamically via MCTP associations.\n\nA recent commit enforced that both \"mi_basic\" and \"mi_i2c\" require\nthe \"Bus\" property upfront, which caused valid \"mi_i2c\" reactor\nconfigurations lacking the \"Bus\" property to be skipped.\n\nThis change separates the protocol validation logic so that \"mi_i2c\"\nonly enforces the presence of \"Bus\" when the device is not an MCTP\nreactor device, restoring backward compatibility.\n\nTested:\n- Added a temporary unit test simulating NVMe configurations with\n  Protocol \"mi_i2c\" and MctpReactorConfigPath without a \"Bus\" property,\n  verifying that the NVMeSubsystem and NVMeDevice are created.\n- Verified that direct \"mi_i2c\" (without MCTP reactor config) and\n  \"mi_basic\" configurations without \"Bus\" continue to be rejected.\n\nGoogle-Bug-Id: 546682451\nChange-Id: I6db4c1a47860b6ac1e8ccf5393f3230ba85b8642\nSigned-off-by: Hao Jiang \u003cjianghao@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d63b2687e16c9a39ebdce288d1667f414065f432",
      "old_mode": 57344,
      "old_path": "dbus-sensors",
      "new_id": "855705fe5ecfff41d1c442717e0fb68459147264",
      "new_mode": 57344,
      "new_path": "dbus-sensors"
    }
  ]
}