diff options
| author | Lee, Chun-Yi <joeyli.kernel@gmail.com> | 2014-09-04 15:13:39 +0800 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2014-09-08 15:38:41 +0200 |
| commit | 9389f46e9782ea5e56fbd7b2e59ba7c08f3ba86b (patch) | |
| tree | f3221dc16182f9dc090f3d85c3e41e45181bbe9a /drivers/acpi/acpi_cmos_rtc.c | |
| parent | 2ce7598c9a453e0acd0e07be7be3f5eb39608ebd (diff) | |
| download | linux-9389f46e9782ea5e56fbd7b2e59ba7c08f3ba86b.tar.gz linux-9389f46e9782ea5e56fbd7b2e59ba7c08f3ba86b.tar.bz2 linux-9389f46e9782ea5e56fbd7b2e59ba7c08f3ba86b.zip | |
ACPI / RTC: Fix CMOS RTC opregion handler accesses to wrong addresses
The value64 parameter is an u64 point that used to transfer the value
for write to CMOS, or used to return the value that's read from CMOS.
The value64 is an u64 point, so don't need get address again. It causes
acpi_cmos_rtc_space_handler always return 0 to reader and didn't write
expected value to CMOS.
Signed-off-by: Lee, Chun-Yi <jlee@suse.com>
Cc: 3.11+ <stable@vger.kernel.org> # 3.11+
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/acpi/acpi_cmos_rtc.c')
| -rw-r--r-- | drivers/acpi/acpi_cmos_rtc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/acpi/acpi_cmos_rtc.c b/drivers/acpi/acpi_cmos_rtc.c index 2da8660262e5..81dc75033f15 100644 --- a/drivers/acpi/acpi_cmos_rtc.c +++ b/drivers/acpi/acpi_cmos_rtc.c @@ -33,7 +33,7 @@ acpi_cmos_rtc_space_handler(u32 function, acpi_physical_address address, void *handler_context, void *region_context) { int i; - u8 *value = (u8 *)&value64; + u8 *value = (u8 *)value64; if (address > 0xff || !value64) return AE_BAD_PARAMETER; |