Re: [PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

2017-03-21 Thread Jonathan Cameron
On 21/03/17 15:05, SIMRAN SINGHAL wrote: > On Tue, Mar 21, 2017 at 8:01 PM, kbuild test robot wrote: >> Hi simran, >> >> [auto build test WARNING on iio/togreg] >> [also build test WARNING on v4.11-rc3 next-20170321] >> [if your patch is applied to the wrong git tree, please drop

Re: [PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

2017-03-21 Thread SIMRAN SINGHAL
On Tue, Mar 21, 2017 at 8:01 PM, kbuild test robot wrote: > Hi simran, > > [auto build test WARNING on iio/togreg] > [also build test WARNING on v4.11-rc3 next-20170321] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > >

Re: [PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

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

Re: [Outreachy kernel] [PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

2017-03-19 Thread SIMRAN SINGHAL
On Mon, Mar 20, 2017 at 2:13 AM, Jonathan Cameron wrote: > On 19/03/17 17:14, Gargi Sharma wrote: >> On Sun, Mar 19, 2017 at 6:20 PM, simran singhal >> wrote: >>> The IIO subsystem is redefining iio_dev->mlock to be used by >>> the IIO core only for

Re: [Outreachy kernel] [PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

2017-03-19 Thread Jonathan Cameron
On 19/03/17 17:14, Gargi Sharma wrote: > On Sun, Mar 19, 2017 at 6:20 PM, 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,

Re: [Outreachy kernel] [PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

2017-03-19 Thread Gargi Sharma
On Sun, Mar 19, 2017 at 6:20 PM, 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,

[PATCH v5] staging: Use buf_lock instead of mlock and Refactor code

2017-03-19 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