Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752397AbdCMOHe (ORCPT ); Mon, 13 Mar 2017 10:07:34 -0400 Received: from mail-it0-f50.google.com ([209.85.214.50]:37575 "EHLO mail-it0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751154AbdCMOHY (ORCPT ); Mon, 13 Mar 2017 10:07:24 -0400 MIME-Version: 1.0 In-Reply-To: <20170313115129.GC4136@mwanda> References: <20170313105421.GA32342@SEL-JYOUN-D1> <20170313115129.GC4136@mwanda> From: DaeSeok Youn Date: Mon, 13 Mar 2017 23:07:22 +0900 Message-ID: Subject: Re: [PATCH] staging: atomisp: use k{v}zalloc instead of k{v}alloc and memset To: Dan Carpenter Cc: mchehab@kernel.org, devel , Greg KH , kernel-janitors , linux-kernel , alan@linux.intel.com, linux-media@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 696 Lines: 21 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 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(, 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(). Thanks. Regards, Daeseok Youn > > regards, > dan carpenter >