Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262319AbUK3U7E (ORCPT ); Tue, 30 Nov 2004 15:59:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262311AbUK3U5G (ORCPT ); Tue, 30 Nov 2004 15:57:06 -0500 Received: from fw.osdl.org ([65.172.181.6]:30368 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S262315AbUK3U4r (ORCPT ); Tue, 30 Nov 2004 15:56:47 -0500 Date: Tue, 30 Nov 2004 12:56:33 -0800 (PST) From: Linus Torvalds To: Alexandre Oliva cc: David Howells , Paul Mackerras , Greg KH , David Woodhouse , Matthew Wilcox , hch@infradead.org, linux-kernel@vger.kernel.org, libc-hacker@sources.redhat.com Subject: Re: [RFC] Splitting kernel headers and deprecating __KERNEL__ In-Reply-To: Message-ID: References: <19865.1101395592@redhat.com> <20041125165433.GA2849@parcelfarce.linux.theplanet.co.uk> <1101406661.8191.9390.camel@hades.cambridge.redhat.com> <20041127032403.GB10536@kroah.com> <16810.24893.747522.656073@cargo.ozlabs.ibm.com> <8219.1101828816@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1842 Lines: 43 On Tue, 30 Nov 2004, Alexandre Oliva wrote: > > - move anything that is not protected by #ifdef __KERNEL__ to the > ukabi header tree, adding an include in the beginning of the original > header that includes the ukabi header. No. I want stuff that goes into the ABI tree to be clearly _defined_ to be user-visible. Not a "let's move it all there and then prune it". Leave anything questionable in the current location. And never EVER move anything that is kernel-internal to a new "clean" tree, because that would be totally pointless. At that point, people would have to edit the "clean" tree even for kernel internal stuff. No go. Also, "ukabi" just isn't going to fly as a name. It's also not as simple as you seem to think, since a lot of these ABI things are architecture- dependent, which apparently all you guys have totally ignored. I've suggested "include/user/" and "include/asm-xxx/user", which handles architecture-specific parts too. I'm ok with doing it the other way around, ie "include/user/" and "include/user/arch-xxxx". And "user" might be "user-abi" or something like that, but it sure isn't going to be some unreadable contraction. And I _still_ want to see these patches only for things where somebody can validly argue that (a) it can't break anything (ie the old location still includes the new one, exactly the same way) (b) there are people who will actually take _advantage_ of that particular file (ie "just because I think so" doesn't fly). Moving files around is just too disruptive to be done without damn good reason. Linus - 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/