)]}'
{
  "commit": "5b02aa1e6e7cf7d3bbf8027dc7e05e0eb2f1e828",
  "tree": "447c7f9a618aac8f6e8eb79dc7fa641c619232f8",
  "parents": [
    "69e8f430e243d657c2053f097efebc2e2cd559f0"
  ],
  "author": {
    "name": "Konrad Rzeszutek Wilk",
    "email": "konrad.wilk@oracle.com",
    "time": "Wed Feb 01 16:07:41 2012 -0500"
  },
  "committer": {
    "name": "Konrad Rzeszutek Wilk",
    "email": "konrad.wilk@oracle.com",
    "time": "Fri Feb 03 16:05:30 2012 -0500"
  },
  "message": "xen/bootup: During bootup suppress XENBUS: Unable to read cpu state\n\nWhen the initial domain starts, it prints (depending on the\namount of CPUs) a slew of\nXENBUS: Unable to read cpu state\nXENBUS: Unable to read cpu state\nXENBUS: Unable to read cpu state\nXENBUS: Unable to read cpu state\n\nwhich provide no useful information - as the error is a valid\nissue - but not on the initial domain. The reason is that the\nXenStore is not accessible at that time (it is after all the\nfirst guest) so the CPU hotplug watch cannot parse \"availability/cpu\"\nattribute.\n\nSigned-off-by: Konrad Rzeszutek Wilk \u003ckonrad.wilk@oracle.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "14e2d995e95800ca88a064ac5ba09caec2b48973",
      "old_mode": 33188,
      "old_path": "drivers/xen/cpu_hotplug.c",
      "new_id": "4dcfced107f50e41c518405b28747064d62d78bc",
      "new_mode": 33188,
      "new_path": "drivers/xen/cpu_hotplug.c"
    }
  ]
}