From: Chris Friesen <cfriesen@nortelnetworks.com>
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
Date: Fri, 01 Oct 2004 10:31:29 -0600 [thread overview]
Message-ID: <415D8661.3000406@nortelnetworks.com> (raw)
In-Reply-To: <20041001091325.7fbc6971.pj@sgi.com>
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
next prev parent reply other threads:[~2004-10-01 16:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 22:33 [RFC][PATCH] inotify 0.11.0 [WITH PATCH!] John McCutchan
2004-09-30 19:01 ` [patch] inotify: locking Robert Love
2004-09-30 19:17 ` Robert Love
2004-09-30 21:36 ` [patch] inotify: ioctl makeover Robert Love
2004-09-30 22:25 ` [patch] inotify: make user visible types portable Robert Love
2004-09-30 22:30 ` Robert Love
2004-10-02 9:21 ` David Woodhouse
2004-09-30 22:57 ` Paul Jackson
2004-10-01 5:35 ` Robert Love
2004-10-01 6:44 ` Paul Jackson
2004-10-01 7:39 ` Robert Love
2004-10-01 15:40 ` Paul Jackson
2004-10-01 15:47 ` Robert Love
2004-10-01 16:13 ` Paul Jackson
2004-10-01 16:31 ` Chris Friesen [this message]
2004-10-01 18:00 ` Paul Jackson
2004-09-30 22:43 ` [patch] inotify: rename inotify_watcher Robert Love
2004-09-30 22:44 ` Robert Love
2004-09-30 22:53 ` [patch] inotify: rename slab-related stuff Robert Love
2004-10-01 17:46 ` [patch] inotify: misc changes Robert Love
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=415D8661.3000406@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=rml@novell.com \
--cc=ttb@tentacle.dhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox