)]}'
{
  "commit": "9a281a677c1dbf25943b5bc3225de21fcb4945ae",
  "tree": "2923528b76a0f27e6244ff58daf4c80cb3e32f20",
  "parents": [
    "92d921c5def1a7b1411bc54859c0771b2cf2c08d"
  ],
  "author": {
    "name": "John Stultz",
    "email": "john.stultz@linaro.org",
    "time": "Fri May 06 17:21:12 2011 -0700"
  },
  "committer": {
    "name": "John Stultz",
    "email": "john.stultz@linaro.org",
    "time": "Fri May 06 17:42:47 2011 -0700"
  },
  "message": "rtc: ds1286: Initialize drvdata before registering device\n\nCommit f44f7f96a20 (\"RTC: Initialize kernel state from RTC\") uncovered\nan issue in a number of RTC drivers, where the drivers call\nrtc_device_register before initializing the device or platform drvdata.\n\nThis frequently results in null pointer dereferences when the\nrtc_device_register immediately makes use of the rtc device, calling\nrtc_read_alarm.\n\nThe solution is to ensure the drvdata is initialized prior to registering\nthe rtc device.\n\nCC: Wolfram Sang \u003cw.sang@pengutronix.de\u003e\nCC: Alessandro Zummo \u003ca.zummo@towertech.it\u003e\nCC: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCC: rtc-linux@googlegroups.com\nSigned-off-by: John Stultz \u003cjohn.stultz@linaro.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "60ce69600828237e63175a7aed8962a6d463a86e",
      "old_mode": 33188,
      "old_path": "drivers/rtc/rtc-ds1286.c",
      "new_id": "47e681df31e280d27f4ce1a926b0f1c5bedbc13e",
      "new_mode": 33188,
      "new_path": "drivers/rtc/rtc-ds1286.c"
    }
  ]
}