From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 28 Nov 2006 11:11:58 -0800 (PST) From: Christoph Lameter Subject: Re: [RFC] Extract kmalloc.h and slob.h from slab.h In-Reply-To: Message-ID: References: <84144f020611280000w26d74321i2804b3d04b87762@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Pekka J Enberg Cc: akpm@osdl.org, linux-mm@kvack.org, mpm@selenic.com, Manfred Spraul List-ID: On Tue, 28 Nov 2006, Pekka J Enberg wrote: > I don't think should have either but I suppose there can be > other (broken) headers that include it and thus its safer not to remove > the guard clause just yet. However, if you wrap the include of > header inside the existing guard then we should be fine, > no? There could be other header files used by user space where we would want to switch from slab.h to kmalloc.h in the future. All three header files are pretty low level and so we will have frequent includes. I think it is safer to have the guard in there. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org