Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262198AbVDFNK6 (ORCPT ); Wed, 6 Apr 2005 09:10:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262200AbVDFNK6 (ORCPT ); Wed, 6 Apr 2005 09:10:58 -0400 Received: from wproxy.gmail.com ([64.233.184.205]:21911 "EHLO wproxy.gmail.com") by vger.kernel.org with ESMTP id S262198AbVDFNKx (ORCPT ); Wed, 6 Apr 2005 09:10:53 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=lQ4JNqhTINw3WnHJ6a13FQvpNMKklnLcCvU77qvOaqNyoD7XQqWnPEB8nUn7AKVfA4Udi2ex6fkdyFy78jI9beAi3nNnGTzWJvV/lfbmQ1WfxAt1iwTTDHsqojXxI1DZFcP4qIR4NYZEEiwx2Rwto/+DARE9/0QxEq2Iyjlk+UQ= Message-ID: <84144f02050406061077de4c2e@mail.gmail.com> Date: Wed, 6 Apr 2005 16:10:52 +0300 From: Pekka Enberg Reply-To: Pekka Enberg To: Paulo Marques Subject: Re: RFC: turn kmalloc+memset(,0,) into kcalloc Cc: =?ISO-8859-1?Q?J=F6rn_Engel?= , Jesper Juhl , Roland Dreier , LKML , penberg@cs.helsinki.fi In-Reply-To: <4253D2CD.2040600@grupopie.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <4252BC37.8030306@grupopie.com> <521x9pc9o6.fsf@topspin.com> <20050406112837.GC7031@wohnheim.fh-wedel.de> <4253D2CD.2040600@grupopie.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 732 Lines: 17 Hi, On Apr 6, 2005 3:15 PM, Paulo Marques wrote: > However "calloc" is the standard C interface for doing this, so it makes > some sense to use it here as well... :( I initally submitted kcalloc() with just one parameter but Arjan wanted it to be similar to standard calloc() so we could check for overflows. I don't see any reason not to introduce kzalloc() for the common case you mentioned (as suggested by Denis). Pekka - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/