Re: [PATCH v7] staging: adis16060_core: Replace mlock with buf_lock and refactor code

2017-03-22 Thread Jonathan Cameron
On 22/03/17 20:00, kbuild test robot wrote: > Hi simran, > > [auto build test WARNING on iio/togreg] > [also build test WARNING on v4.11-rc3 next-20170322] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: >

Re: [PATCH v7] staging: adis16060_core: Replace mlock with buf_lock and refactor code

2017-03-22 Thread kbuild test robot
Hi simran, [auto build test WARNING on iio/togreg] [also build test WARNING on v4.11-rc3 next-20170322] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v7] staging: adis16060_core: Replace mlock with buf_lock and refactor code

2017-03-21 Thread Jonathan Cameron
On 20/03/17 12:53, simran singhal wrote: > The IIO subsystem is redefining iio_dev->mlock to be used by > the IIO core only for protecting device operating mode changes. > ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes. > > In this driver, mlock was being used to protect hardware

[PATCH v7] staging: adis16060_core: Replace mlock with buf_lock and refactor code

2017-03-20 Thread simran singhal
The IIO subsystem is redefining iio_dev->mlock to be used by the IIO core only for protecting device operating mode changes. ie. Changes between INDIO_DIRECT_MODE, INDIO_BUFFER_* modes. In this driver, mlock was being used to protect hardware state changes. Replace it with buf_lock in the devices