From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261672AbUK2LM1 (ORCPT ); Mon, 29 Nov 2004 06:12:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261666AbUK2LLC (ORCPT ); Mon, 29 Nov 2004 06:11:02 -0500 Received: from mx1.redhat.com ([66.187.233.31]:63713 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S261656AbUK2LJV (ORCPT ); Mon, 29 Nov 2004 06:09:21 -0500 From: David Howells In-Reply-To: References: <19865.1101395592@redhat.com> To: Grzegorz Kulewski Cc: torvalds@osdl.org, hch@infradead.org, matthew@wil.cx, dwmw2@infradead.org, aoliva@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [RFC] Splitting kernel headers and deprecating __KERNEL__ User-Agent: EMH/1.14.1 SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3 (i386-redhat-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Date: Mon, 29 Nov 2004 11:08:34 +0000 Message-ID: <12917.1101726514@redhat.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Grzegorz Kulewski : > > (b) Make kernel file #include the user file. > > Does kernel really need to include user headers? When it is definition of > some const then it should be defined in one file (to be sure it has only > one definition). But user headers may have some compatibility hacks that > kernel do not need (and even maybe does not want) to have. > > How you will handle that? I must have mis-explained it. I meant: > > (b) Make kernel file #include the user/ file. I don't actually mean that the kernel should in anyway touch userspace headers. I was referring to the bits split out into user-xxxx/ directories. David