Re: [PATCH v6 1/4] gpiolib: Pass bitmaps, not integer arrays, to get/set array

2018-09-04 Thread kbuild test robot
Hi Janusz, Thank you for the patch! Yet something to improve: [auto build test ERROR on gpio/for-next] [also build test ERROR on v4.19-rc2 next-20180831] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v6 1/4] gpiolib: Pass bitmaps, not integer arrays, to get/set array

2018-09-04 Thread kbuild test robot
Hi Janusz, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on gpio/for-next] [also build test WARNING on v4.19-rc2 next-20180831] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v6 1/4] gpiolib: Pass bitmaps, not integer arrays, to get/set array

2018-08-31 Thread Peter Rosin
On 2018-09-01 00:56, Janusz Krzysztofik wrote: > Most users of get/set array functions iterate consecutive bits of data, > usually a single integer, while processing array of results obtained > from, or building an array of values to be passed to those functions. > Save time wasted on those

[PATCH v6 1/4] gpiolib: Pass bitmaps, not integer arrays, to get/set array

2018-08-31 Thread Janusz Krzysztofik
Most users of get/set array functions iterate consecutive bits of data, usually a single integer, while processing array of results obtained from, or building an array of values to be passed to those functions. Save time wasted on those iterations by changing the functions' API to accept bitmaps.