diff options
| author | John Stultz <john.stultz@linaro.org> | 2011-05-06 17:27:07 -0700 |
|---|---|---|
| committer | John Stultz <john.stultz@linaro.org> | 2011-05-06 18:02:02 -0700 |
| commit | 03cf7c477de8cb47658ba93f33dc93242985acff (patch) | |
| tree | 48333856db52805ac61064ee0452809f3b606e1e /Kconfig | |
| parent | 2f5c4fe8f9811152d69ef5cd020e095a1f84ca65 (diff) | |
| download | linux-stable-03cf7c477de8cb47658ba93f33dc93242985acff.tar.gz linux-stable-03cf7c477de8cb47658ba93f33dc93242985acff.tar.bz2 linux-stable-03cf7c477de8cb47658ba93f33dc93242985acff.zip | |
rtc: max8998: Initialize drvdata before registering device
Commit f44f7f96a20 ("RTC: Initialize kernel state from RTC") uncovered
an issue in a number of RTC drivers, where the drivers call
rtc_device_register before initializing the device or platform drvdata.
This frequently results in null pointer dereferences when the
rtc_device_register immediately makes use of the rtc device, calling
rtc_read_alarm.
The solution is to ensure the drvdata is initialized prior to registering
the rtc device.
CC: Wolfram Sang <w.sang@pengutronix.de>
CC: Alessandro Zummo <a.zummo@towertech.it>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: rtc-linux@googlegroups.com
Signed-off-by: John Stultz <john.stultz@linaro.org>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions