From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932756AbVINTUs (ORCPT ); Wed, 14 Sep 2005 15:20:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932757AbVINTUs (ORCPT ); Wed, 14 Sep 2005 15:20:48 -0400 Received: from terminus.zytor.com ([209.128.68.124]:10974 "EHLO terminus.zytor.com") by vger.kernel.org with ESMTP id S932756AbVINTUr (ORCPT ); Wed, 14 Sep 2005 15:20:47 -0400 Message-ID: <43287800.3040108@zytor.com> Date: Wed, 14 Sep 2005 12:20:32 -0700 From: "H. Peter Anvin" User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "linux-os (Dick Johnson)" CC: Kyle Moffett , Bill Davidsen , Linux Kernel Mailing List Subject: Re: [RFC] Splitting out kernel<=>userspace ABI headers References: <20050902134108.GA16374@codepoet.org> <22D79100-00B5-44F6-992C-FFFEACA49E66@mac.com> <20050902235833.GA28238@codepoet.org> <4328299C.9020904@tmr.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org linux-os (Dick Johnson) wrote: > > No No. The solution is to do it right. If the standard says that > the header file can't include a header file defining the types used > within that header file (and I don't think the "standard" says that > at all), then the correct solution is to include the correct header file > in the user program. It is truly just that simple. > Dear Wrongbot, No, it's not that simple. -hpa