From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754100AbcEZOdj (ORCPT ); Thu, 26 May 2016 10:33:39 -0400 Received: from b.ns.miles-group.at ([95.130.255.144]:44723 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753670AbcEZOdi (ORCPT ); Thu, 26 May 2016 10:33:38 -0400 Subject: Re: [PATCH V2] fs: ubifs: Replace kmem_cache_alloc/memset with kmem_cache_zalloc To: Salah Triki , dedekind1@gmail.com, adrian.hunter@intel.com References: <1464272937-6629-1-git-send-email-salah.triki@acm.org> Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org From: Richard Weinberger Message-ID: <5747093D.50508@nod.at> Date: Thu, 26 May 2016 16:33:33 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <1464272937-6629-1-git-send-email-salah.triki@acm.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 26.05.2016 um 16:28 schrieb Salah Triki: > Code is more readable when using kmem_cache_zalloc instead of kmem_cache_alloc/memset. I don't fully agree. You also have ignored my other comment on this patch. Please note that the path you are patching is a hot path. Thanks, //richard