Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759708AbXHBShX (ORCPT ); Thu, 2 Aug 2007 14:37:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754087AbXHBShK (ORCPT ); Thu, 2 Aug 2007 14:37:10 -0400 Received: from smtp2.linux-foundation.org ([207.189.120.14]:41264 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755541AbXHBShJ (ORCPT ); Thu, 2 Aug 2007 14:37:09 -0400 Date: Thu, 2 Aug 2007 11:36:26 -0700 From: Andrew Morton To: Miklos Szeredi Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, torvalds@linux-foundation.org Subject: Re: [PATCH] type safe allocator Message-Id: <20070802113626.634a6bd9.akpm@linux-foundation.org> In-Reply-To: References: X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.6; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1082 Lines: 28 On Thu, 02 Aug 2007 13:31:56 +0200 Miklos Szeredi wrote: > The linux kernel doesn't have a type safe object allocator a-la new() > in C++ or g_new() in glib. > > Introduce two helpers for this purpose: > > alloc_struct(type, gfp_flags); > > zalloc_struct(type, gfp_flags); whimper. On a practical note, I'm still buried in convert-to-kzalloc patches, and your proposal invites a two-year stream of 10,000 convert-to-alloc_struct patches. So if this goes in (and I can't say I'm terribly excited about the idea) then I think we'd also need a maintainer who is going to handle all the subsequent patches, run a git tree, (a quilt tree would be better, or maybe a git tree with 100 branches), work with all the affected maintainers, make sure there aren't clashes with other people's work and all that blah. - 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/