tosa_battery: Fix build error due to direct driver_data usage
authorDmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Tue, 27 Apr 2010 13:18:22 +0000 (17:18 +0400)
committerAnton Vorontsov <cbouatmailru@gmail.com>
Sun, 2 May 2010 20:02:56 +0000 (00:02 +0400)
commit06b9e650ce5eaf14ac1486b2f05baaf2ba22ad22
tree5ab82cff7ea81237f55393bd7c2dcb974ed731d9
parentb1458fb57de03b19296cac70e9455b05912782b5
tosa_battery: Fix build error due to direct driver_data usage

The driver isn't buildable since 2.6.32 (i.e. commit b4028437
"Driver core: move dev_get/set_drvdata to drivers/base/dd.c"):

  CC      tosa_battery.o
tosa_battery.c: In function 'tosa_read_bat':
tosa_battery.c:64: error: 'struct device' has no member named 'driver_data'
tosa_battery.c: In function 'tosa_read_temp':
tosa_battery.c:84: error: 'struct device' has no member named 'driver_data'

Nowadays we must not access driver_data directly, use dev_get_drvdata()
instead.

Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Anton Vorontsov <cbouatmailru@gmail.com>
drivers/power/tosa_battery.c