)]}'
{
  "commit": "4d13ae45ff93fa825ceb39dfd16b305f4baccd18",
  "tree": "6643cd405cc10b1e166d5e84e48d85b2fe4d2b2e",
  "parents": [
    "59084feb256c617063e0dbe7e64821ae8852d7cf"
  ],
  "author": {
    "name": "David Hildenbrand",
    "email": "david@redhat.com",
    "time": "Tue Apr 16 16:14:26 2024 +0200"
  },
  "committer": {
    "name": "David Hildenbrand",
    "email": "david@redhat.com",
    "time": "Wed Jul 10 18:06:24 2024 +0200"
  },
  "message": "virtio-mem: improve error message when unplug of device fails due to plugged memory\n\nThe error message is actually expressive, considering QEMU only. But\nwhen called from Libvirt, talking about \"size\" can be confusing, because\nin Libvirt \"size\" translates to the memory backend size in QEMU (maximum\nsize) and \"current\" translates to the QEMU \"size\" property.\n\nLet\u0027s simply avoid talking about the \"size\" property and spell out that\nsome device memory is still plugged.\n\nMessage-ID: \u003c20240416141426.588544-1-david@redhat.com\u003e\nTested-by: Mario Casquero \u003cmcasquer@redhat.com\u003e\nCc: Liang Cong \u003clcong@redhat.com\u003e\nCc: Mario Casquero \u003cmcasquer@redhat.com\u003e\nCc: \"Michael S. Tsirkin\" \u003cmst@redhat.com\u003e\nSigned-off-by: David Hildenbrand \u003cdavid@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ffd119ebacb766773322137a82bb64e1bb7e7b14",
      "old_mode": 33188,
      "old_path": "hw/virtio/virtio-mem.c",
      "new_id": "ef64bf1b4a1a5508e84baeef1a9f919787b2aecd",
      "new_mode": 33188,
      "new_path": "hw/virtio/virtio-mem.c"
    }
  ]
}