)]}'
{
  "commit": "5d739a4787a53da8d787551c8de27ad39fabdb34",
  "tree": "a6aba59c3fc6e2a76978686dc3453fc3980e8b24",
  "parents": [
    "d1028f1b5b4cf83e8af5f48996cf392fb12d391a"
  ],
  "author": {
    "name": "Christian Borntraeger",
    "email": "borntraeger@de.ibm.com",
    "time": "Tue Feb 11 22:46:53 2014 +0100"
  },
  "committer": {
    "name": "Christian Borntraeger",
    "email": "borntraeger@de.ibm.com",
    "time": "Thu Feb 27 09:51:26 2014 +0100"
  },
  "message": "s390-ccw.img: Fix sporadic errors with ccw boot image - initialize css\n\nWe have to set the cssid to 0, otherwise the stsch code will\nreturn an operand exception without the m bit. In the same way\nwe should set m\u003d0.\n\nThis case was triggered in some cases during reboot, if for some\nreason the location of blk_schid.cssid contains 1 and m was 0.\nTurns out that the qemu elf loader does not zero out the bss section\non reboot.\n\nThe symptom was an dump of the old kernel with several areas\noverwritten. The bootloader does not register a program check\nhandler, so bios exception jumped back into the old kernel.\n\nLets just use a local struct with a designed initializer. That\nwill guarantee that all other subelements are initialized to 0.\n\nSigned-off-by: Christian Borntraeger \u003cborntraeger@de.ibm.com\u003e\nReviewed-by: Cornelia Huck \u003ccornelia.huck@de.ibm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c5d533231b903f1fd1991c37ca6379d7019a4042",
      "old_mode": 33188,
      "old_path": "pc-bios/s390-ccw/main.c",
      "new_id": "5c3376653345d6ac3123049bbf2c4a37500e411f",
      "new_mode": 33188,
      "new_path": "pc-bios/s390-ccw/main.c"
    }
  ]
}