staging: iio: lis3l02dq - incorrect ws used in container of call.
commit0b64c38b71d6e2c1049c75bb1d885031008700c1
authorJonathan Cameron <jic23@cam.ac.uk>
Thu, 11 Mar 2010 17:29:48 +0000 (11 17:29 +0000)
committerGreg Kroah-Hartman <gregkh@suse.de>
Fri, 30 Apr 2010 16:30:08 +0000 (30 09:30 -0700)
tree89ae7febca23ebc3c161fac9b2b5a2370c5a2b38
parent66f41d4c5c8a5deed66fdcc84509376c9a0bf9d8
staging: iio: lis3l02dq - incorrect ws used in container of call.

The word oops comes to mind.  Original patch to merge the two work queues
in here (prior to Greg taking them into staging) changed the top half to
only use one of them and the bottom half to assume it was the other.

Currently causes a NULL pointer dereference if you enable any of the events
on an lis3l02dq. Just goes to show I need a few more regression tests.

Signed-of-by: Jonathan Cameron <jic23@cam.ac.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/staging/iio/accel/lis3l02dq_core.c