staging:iio:trigger: Use to_iio_trigger() instead of dev_get_drvdata()
authorLars-Peter Clausen <lars@metafoo.de>
Thu, 21 Jun 2012 17:10:59 +0000 (19:10 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 23 Jun 2012 04:08:10 +0000 (21:08 -0700)
commit4bf8172772254a38741de139a355e36eabbb5cb8
tree7777ff682c067c911ac208409e6601f37cdb7c43
parent70b3fd34a9b2e06b2702d691d406ef2ec1d2f0df
staging:iio:trigger: Use to_iio_trigger() instead of dev_get_drvdata()

Use to_iio_trigger(dev) instead of dev_get_drvdata(dev). Both will return the
trigger which belongs to the device, but the the first on is a bit more
lightweight. Also this will eventually free up the drvdata pointer of the device
for driver specific data.

Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Acked-by: Jonathan Cameron <jic23@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/staging/iio/trigger/iio-trig-bfin-timer.c
drivers/staging/iio/trigger/iio-trig-periodic-rtc.c
drivers/staging/iio/trigger/iio-trig-sysfs.c