[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHb8M2CwfTN-dx4ojUJCvF_jr0E1bo4KLWpZE74y45WkV_6C+A@mail.gmail.com>
Date: Tue, 14 Mar 2017 00:40:01 +0900
From: DaeSeok Youn <daeseok.youn@...il.com>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: mchehab@...nel.org, devel <devel@...verdev.osuosl.org>,
Greg KH <gregkh@...uxfoundation.org>,
kernel-janitors <kernel-janitors@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
alan@...ux.intel.com, linux-media@...r.kernel.org
Subject: 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 <daeseok.youn@...il.com>:
> 2017-03-13 20:51 GMT+09:00 Dan Carpenter <dan.carpenter@...cle.com>:
>> 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 reason with kzalloc)
>>>
>>> And also atomisp_kernel_malloc() can be used with
>>> atomisp_kernel_zalloc(<size>, false);
>>>
>>
>> We should just change all the callers to kvmalloc() and kvzmalloc().
> ok. I will try to change all the callers to kvmalloc() and kvzalloc().
The kvmalloc() and kvzalloc() are not ready to use in staging-testing
branch on staging tree.
If the kvmalloc and kvzalloc are available to use, I will replace
atomisp_kernel_malloc() and atomisp_kernel_zalloc() with kvmalloc()
and kvzalloc().
Thanks.
Regards,
Daeseok Youn.
>
> Thanks.
> Regards,
> Daeseok Youn
>>
>> regards,
>> dan carpenter
>>
Powered by blists - more mailing lists