From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by ug-out-1314.google.com with SMTP id s2so1378429uge for ; Tue, 28 Nov 2006 11:32:04 -0800 (PST) Message-ID: <84144f020611281132p5f3f042dq36728c78521efb57@mail.gmail.com> Date: Tue, 28 Nov 2006 21:32:03 +0200 From: "Pekka Enberg" Subject: Re: Re: [RFC] Extract kmalloc.h and slob.h from slab.h In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <84144f020611280000w26d74321i2804b3d04b87762@mail.gmail.com> Sender: owner-linux-mm@kvack.org Return-Path: To: Christoph Lameter Cc: akpm@osdl.org, linux-mm@kvack.org, mpm@selenic.com, Manfred Spraul List-ID: On 11/28/06, Christoph Lameter wrote: > A userspace header can use linux/blablabla.h and may > then include And that's a broken userspace header all the same. I do see the point of keeping as is for compatability but why would we want to repeat the same mistake in a new interface? If we really do _need_ to convert existing broken userspace headers to use we can always fix it locally. So can we drop the guard clause? Pretty please and sugar on the top. -- 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