Re: [PATCH] staging: atomisp: use k{v}zalloc instead of k{v}alloc and memset

2017-03-14 2:54 GMT+09:00 Alan Cox : > > On Mon, 2017-03-13 at 19:54 +0900, Daeseok Youn wrote: > > If the atomisp_kernel_zalloc() has "true" as a second parameter, it > > tries to allocate zeroing memory from kmalloc(vmalloc) and memset. > > But using kzalloc is rather than

Re: [PATCH] staging: atomisp: use k{v}zalloc instead of k{v}alloc and memset

On Mon, 2017-03-13 at 19:54 +0900, Daeseok Youn wrote: > If the atomisp_kernel_zalloc() has "true" as a second parameter, it > tries to allocate zeroing memory from kmalloc(vmalloc) and memset. > But using kzalloc is rather than kmalloc followed by memset with 0. > (vzalloc is for same reason with

Re: [PATCH] staging: atomisp: use k{v}zalloc instead of k{v}alloc and memset

2017-03-13 23:07 GMT+09:00 DaeSeok Youn : > 2017-03-13 20:51 GMT+09:00 Dan Carpenter : >> On Mon, Mar 13, 2017 at 07:54:21PM +0900, Daeseok Youn wrote: >>> If the atomisp_kernel_zalloc() has "true" as a second parameter, it >>> tries to allocate

Re: [PATCH] staging: atomisp: use k{v}zalloc instead of k{v}alloc and memset

2017-03-13 20:51 GMT+09:00 Dan Carpenter : > On Mon, Mar 13, 2017 at 07:54:21PM +0900, Daeseok Youn wrote: >> If the atomisp_kernel_zalloc() has "true" as a second parameter, it >> tries to allocate zeroing memory from kmalloc(vmalloc) and memset. >> But using kzalloc is

Re: [PATCH] staging: atomisp: use k{v}zalloc instead of k{v}alloc and memset

On Mon, Mar 13, 2017 at 07:54:21PM +0900, Daeseok Youn wrote: > If the atomisp_kernel_zalloc() has "true" as a second parameter, it > tries to allocate zeroing memory from kmalloc(vmalloc) and memset. > But using kzalloc is rather than kmalloc followed by memset with 0. > (vzalloc is for same