summaryrefslogtreecommitdiffstats
path: root/drivers/input
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <gregkh@suse.de>2009-05-01 06:41:58 -0700
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2009-05-01 06:49:15 -0700
commit84e5b0d00f8f84c4ae226be131d4bebbcee88bd3 (patch)
tree868b35ad308dcb0fd1a63d88462493a521e4bc28 /drivers/input
parenteb990b5533cfbddfac6efe783a349525907d1c26 (diff)
downloadlinux-84e5b0d00f8f84c4ae226be131d4bebbcee88bd3.tar.gz
linux-84e5b0d00f8f84c4ae226be131d4bebbcee88bd3.tar.bz2
linux-84e5b0d00f8f84c4ae226be131d4bebbcee88bd3.zip
Input: wm97xx - do not access dev->driver_data directly
In the near future, the driver core is going to not allow direct access to the driver_data pointer in struct device. Instead, the functions dev_get_drvdata() and dev_set_drvdata() should be used. These functions have been around since the beginning, so are backwards compatible with all older kernel versions. Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Diffstat (limited to 'drivers/input')
-rw-r--r--drivers/input/touchscreen/wm97xx-core.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/input/touchscreen/wm97xx-core.c b/drivers/input/touchscreen/wm97xx-core.c
index 69af8385ab14..2957d48e0045 100644
--- a/drivers/input/touchscreen/wm97xx-core.c
+++ b/drivers/input/touchscreen/wm97xx-core.c
@@ -569,7 +569,7 @@ static int wm97xx_probe(struct device *dev)
mutex_init(&wm->codec_mutex);
wm->dev = dev;
- dev->driver_data = wm;
+ dev_set_drvdata(dev, wm);
wm->ac97 = to_ac97_t(dev);
/* check that we have a supported codec */