Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 15 Jul 2001 09:12:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 15 Jul 2001 09:12:34 -0400 Received: from weta.f00f.org ([203.167.249.89]:61571 "HELO weta.f00f.org") by vger.kernel.org with SMTP id ; Sun, 15 Jul 2001 09:12:22 -0400 Date: Mon, 16 Jul 2001 01:12:27 +1200 From: Chris Wedgwood To: Kai Henningsen Cc: linux-kernel@vger.kernel.org Subject: Re: __KERNEL__ removal Message-ID: <20010716011227.B10493@weta.f00f.org> In-Reply-To: <3B5083AE.71515696@mandrakesoft.com> <3B508D34.180A07A0@mandrakesoft.com> <84uhW6amw-B@khms.westfalen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <84uhW6amw-B@khms.westfalen.de> User-Agent: Mutt/1.3.18i X-No-Archive: Yes Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jul 15, 2001 at 01:53:00PM +0200, Kai Henningsen wrote: ... but if we are looking for a clean solution to types and constants that are needed to communicate between kernel and user space, IMO the thing to do is to define these in some sort of generic format, and have a tool to generate actual headers from that according to whatever kernel, libc or whoever wants to see. Possibly more than one tool as requirements differ. Too complex, too hard... why not standard headers for the kernel peoplem as that is the origin on the headers and helper comments for others? --cw - 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/