diff options
| author | John Stultz <[email protected]> | 2011-05-06 17:28:36 -0700 |
|---|---|---|
| committer | John Stultz <[email protected]> | 2011-05-06 18:02:03 -0700 |
| commit | 93015236d92bf9ea746c0b10c3c1d9058cb11f82 (patch) | |
| tree | 2e684b034430428a0e3664b58ca9302a34c2b66c /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 03cf7c477de8cb47658ba93f33dc93242985acff (diff) | |
rtc: msm6242: 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 <[email protected]>
CC: Alessandro Zummo <[email protected]>
CC: Thomas Gleixner <[email protected]>
CC: [email protected]
Signed-off-by: John Stultz <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions