Message-ID: <415D8661.3000406@nortelnetworks.com>
Date: Fri, 01 Oct 2004 10:31:29 -0600
From: Chris Friesen <cfriesen@nortelnetworks.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: Paul Jackson <pj@sgi.com>
CC: Robert Love <rml@novell.com>, ttb@tentacle.dhs.org,
       linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [patch] inotify: make user visible types portable
References: <1096410792.4365.3.camel@vertex>	<1096583108.4203.86.camel@betsy.boston.ximian.com>	<20040930155704.16d71cec.pj@sgi.com>	<1096608925.4803.2.camel@localhost>	<20040930234436.097e6dfe.pj@sgi.com>	<1096616399.4803.26.camel@localhost>	<20041001084009.6b33c1a1.pj@sgi.com>	<1096645624.7676.18.camel@betsy.boston.ximian.com> <20041001091325.7fbc6971.pj@sgi.com>
In-Reply-To: <20041001091325.7fbc6971.pj@sgi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 943
Lines: 26

Paul Jackson wrote:
> Robert wrote:
> 
>>The structure needs to be used exactly the same between the kernel and
>>the user.  We both agree to that, right?  It is user visible.
> 
> 
> Certainly the ABI, yes.  These stubborn beasts called computers that we
> labour over just won't work otherwise.
> 
> I'd have no objections to the user header spelling "__u32" where the
> kernel header spelled "u32".

I believe there is a long-term goal to separate out the userspace-visible part 
of the kernel headers into a separate header area, and include them into the kernel.

Even without that, the headers are periodically extracted and cleaned up.  Why 
make that job harder than it needs to be?

Chris

-
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/