Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262367AbUK3WgB (ORCPT ); Tue, 30 Nov 2004 17:36:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262370AbUK3WgB (ORCPT ); Tue, 30 Nov 2004 17:36:01 -0500 Received: from canuck.infradead.org ([205.233.218.70]:25865 "EHLO canuck.infradead.org") by vger.kernel.org with ESMTP id S262367AbUK3Wew (ORCPT ); Tue, 30 Nov 2004 17:34:52 -0500 Subject: Re: [RFC] Splitting kernel headers and deprecating __KERNEL__ From: David Woodhouse To: Linus Torvalds Cc: Alexandre Oliva , dhowells , Paul Mackerras , Greg KH , Matthew Wilcox , hch@infradead.org, linux-kernel@vger.kernel.org, libc-hacker@sources.redhat.com In-Reply-To: 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> Content-Type: text/plain Date: Tue, 30 Nov 2004 22:34:20 +0000 Message-Id: <1101854061.4574.4.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3.dwmw2.1) Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-SRS-Rewrite: SMTP reverse-path rewritten from by canuck.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1140 Lines: 31 On Tue, 2004-11-30 at 14:25 -0800, Linus Torvalds wrote: > > On Tue, 30 Nov 2004, Alexandre Oliva wrote: > > > > (a) it can't break anything (ie the old location still includes the new > > > one, exactly the same way) > > > > You mean it can't break anything in a kernel build, or it can't break > > anything except for userland apps that abused kernel headers and used > > to get away with that? > > It can't break userland either. That depends on your definition of 'break'. It should prevent abuse. To pick a specific example, since you like them: where userland programs are including atomic.h, and hence writing programs which don't compile on some architectures, and which compile on others but silently give non-atomic results, it's perfectly acceptable and indeed advisable to prevent compilation across the board. Some people might call that breakage; I don't. -- dwmw2 - 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/