Re: [PATCH 3/6] bitmap_parselist: rework input string parser

2019-03-26 Thread Mike Travis
On 3/26/2019 2:09 PM, Yuri Norov wrote: + Mike Travis + Thomas Gleixner -- On Tue, Mar 26, 2019 at 12:07:45AM +0300, Yury Norov wrote: The requirement for this rework is to keep the __bitmap_parselist() copy-less and

Re: [PATCH 3/6] bitmap_parselist: rework input string parser

2019-03-26 Thread Yuri Norov
+ Mike Travis + Thomas Gleixner -- On Tue, Mar 26, 2019 at 12:07:45AM +0300, Yury Norov wrote: >> The requirement for this rework is to keep the __bitmap_parselist() >> copy-less and single-pass but make it more readable and

Re: [PATCH 3/6] bitmap_parselist: rework input string parser

2019-03-26 Thread Andy Shevchenko
On Tue, Mar 26, 2019 at 12:07:45AM +0300, Yury Norov wrote: > The requirement for this rework is to keep the __bitmap_parselist() > copy-less and single-pass but make it more readable and maintainable by > splitting into logical parts and removing explicit nested cycles and > opaque local

[PATCH 3/6] bitmap_parselist: rework input string parser

2019-03-25 Thread Yury Norov
The requirement for this rework is to keep the __bitmap_parselist() copy-less and single-pass but make it more readable and maintainable by splitting into logical parts and removing explicit nested cycles and opaque local variables. __bitmap_parselist() can parse userspace inputs and therefore we

[PATCH 3/6] bitmap_parselist: rework input string parser

2019-02-20 Thread Yury Norov
The requirement for this rework is to keep the __bitmap_parselist() copy-less and single-pass but make it more readable and maintainable by splitting into logical parts and removing explicit nested cycles and opaque local variables. __bitmap_parselist() can parse userspace inputs and therefore we