)]}'
{
  "commit": "4b3687f9c18156cdb71729fe4e0c3000f7e4d7de",
  "tree": "d874e58a7cf4bc488707f956d0160b2eaab57b86",
  "parents": [
    "93015236d92bf9ea746c0b10c3c1d9058cb11f82"
  ],
  "author": {
    "name": "John Stultz",
    "email": "john.stultz@linaro.org",
    "time": "Fri May 06 17:30:57 2011 -0700"
  },
  "committer": {
    "name": "John Stultz",
    "email": "john.stultz@linaro.org",
    "time": "Fri May 06 18:02:04 2011 -0700"
  },
  "message": "rtc: pcap: 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": "a633abc428966a91384d92f2613113a3a8861eab",
      "old_mode": 33188,
      "old_path": "drivers/rtc/rtc-pcap.c",
      "new_id": "cd4f198cc2eff921b364eaa1d66ae8b97e7cf5a1",
      "new_mode": 33188,
      "new_path": "drivers/rtc/rtc-pcap.c"
    }
  ]
}