From: "H. Peter Anvin" <hpa@zytor.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: andersen@codepoet.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Splitting out kernel<=>userspace ABI headers
Date: Fri, 02 Sep 2005 22:57:26 -0700 [thread overview]
Message-ID: <43193B46.6080806@zytor.com> (raw)
In-Reply-To: <AFDE003F-F14F-42CE-B964-2E04A4402406@mac.com>
Kyle Moffett wrote:
>
>> The world would be so much nicer a place if user space were free
>> to #include linux/* header files rather than keeping a
>> per-project private copy of all kernel structs of interest.
>
> Exactly! This is why I want to create kcore/* and kabi/* that
> define the appropriate types, then both userspace and the kernel
> could use whatever types fit their fancy, defined in terms of the
> __kcore_ and __kabi_ types, which could be _depended_ on to exist
> because they are guaranteed not to conflict with other namespaces
>
Agreed. We should use well-defined namespaces that won't conflict.
However, I think the __[us][0-9]+ namespace can be considered
well-established.
-hpa
next prev parent reply other threads:[~2005-09-03 5:57 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 3:00 [RFC] Splitting out kernel<=>userspace ABI headers Kyle Moffett
2005-09-02 13:41 ` Erik Andersen
2005-09-02 20:51 ` Kyle Moffett
2005-09-02 23:58 ` Erik Andersen
2005-09-03 0:07 ` H. Peter Anvin
2005-09-03 0:30 ` Kyle Moffett
2005-09-03 0:34 ` H. Peter Anvin
2005-09-03 0:50 ` Kyle Moffett
2005-09-03 4:28 ` Erik Andersen
2005-09-03 5:22 ` H. Peter Anvin
2005-09-03 5:50 ` Erik Andersen
2005-09-03 5:53 ` H. Peter Anvin
2005-09-03 6:41 ` Erik Andersen
2005-09-03 15:01 ` H. Peter Anvin
2005-09-03 15:19 ` H. Peter Anvin
2005-09-03 16:55 ` Kyle Moffett
2005-09-05 16:35 ` H. Peter Anvin
2005-09-05 23:28 ` Kyle Moffett
2005-09-06 1:29 ` [RFC][MEGAPATCH] Change __ASSEMBLY__ to __ASSEMBLER__ (defined by GCC from 2.95 to current CVS) Kyle Moffett
2005-09-10 8:40 ` Kyle Moffett
2005-09-10 8:45 ` Andrew Morton
2005-09-10 17:38 ` Kyle Moffett
2005-09-10 22:04 ` Andrew Morton
2005-09-11 0:33 ` Kyle Moffett
2005-09-11 0:48 ` Andrew Morton
2005-09-11 3:15 ` Kyle Moffett
2005-09-12 8:09 ` Paul Jackson
2005-09-12 15:19 ` H. Peter Anvin
2005-09-12 15:47 ` Paul Jackson
2005-09-12 17:17 ` Sam Ravnborg
2005-09-12 21:14 ` Paul Jackson
2005-09-12 21:39 ` Kyle Moffett
2005-09-12 17:18 ` H. Peter Anvin
2005-09-12 17:51 ` Kyle Moffett
2005-09-12 21:04 ` Paul Jackson
2005-09-14 13:56 ` Bill Davidsen
2005-09-15 21:53 ` Jeremy Fitzhardinge
2005-09-03 5:55 ` [RFC] Splitting out kernel<=>userspace ABI headers Kyle Moffett
2005-09-03 5:57 ` H. Peter Anvin [this message]
2005-09-03 6:05 ` Kyle Moffett
2005-09-03 15:36 ` Denis Vlasenko
2005-09-03 16:33 ` Kyle Moffett
2005-09-03 16:51 ` Denis Vlasenko
2005-09-14 13:46 ` Bill Davidsen
2005-09-14 17:01 ` Sam Ravnborg
2005-09-14 17:01 ` H. Peter Anvin
2005-09-14 18:14 ` Kyle Moffett
2005-09-14 19:09 ` linux-os (Dick Johnson)
2005-09-14 19:20 ` H. Peter Anvin
2005-09-14 19:46 ` Kyle Moffett
2005-09-02 21:42 ` Jeff Dike
2005-09-02 21:55 ` H. Peter Anvin
2005-09-02 22:44 ` Kyle Moffett
2005-09-02 23:24 ` H. Peter Anvin
2005-09-02 23:41 ` Kyle Moffett
2005-09-02 23:53 ` H. Peter Anvin
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=43193B46.6080806@zytor.com \
--to=hpa@zytor.com \
--cc=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
/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