From: Sam Ravnborg <sam@ravnborg.org>
To: Krzysztof Halasa <khc@pm.waw.pl>, linuxabi@zytor.com
Cc: "Chris Friesen" <cfriesen@nortelnetworks.com>,
"Måns Rullgård" <mru@kth.se>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.3.0
Date: Wed, 3 Mar 2004 16:22:13 +0100 [thread overview]
Message-ID: <20040303152213.GA2148@mars.ravnborg.org> (raw)
In-Reply-To: <m37jy4cuaw.fsf@defiant.pm.waw.pl>
[Also sent to linuxabi@zytor.com]
On Mon, Mar 01, 2004 at 07:10:31PM +0100, Krzysztof Halasa wrote:
>
> The "non-problem" here is, IMHO, that the cleaning of kernel headers
> is quite trivial, and thus nobody is interested :-)
The problem is that there is no infrastructure for abi only .h files (mainly).
Matthew Wilcox + others IIRC has already posted a few patches, but I do not see
this happening until 2.7 opens up.
When the proper infrastructure is agreed upon on lot's of people will put some effort
in this janitorial type of work. But imagine all the small mistakes, something we do not
want in 2.6.
IIRC the current agreed scheme is something along the lines of this:
abi/abi-linux/* Userspace relevant parts of include/linux
abi/abi-asm/ symlink to abi/abi-$(ARCH)
abi/abi-i386 i386 specific userland abi
abi/abi-ppc ppc ....
So a header file in include/linux with a counterpart in abi could look like this:
include/linux/wait.h:
#include <abi-linux/wait.h>
#include <linux/config.h>
typedef struct __wait_queue wait_queue_t;
...
abi/abi-linux/wait.h:
#define WNOHANG 0x00000001
#define WUNTRACED 0x00000002
This proposal meets some resistence related to internal issues such as
renaming of internal types etc.
But in the end the gain from a scheme like this outweights the drawbacks - IMHO.
And the backward compatible stuff can be located in abi where it may belong -
if really needed.
Sam
next prev parent reply other threads:[~2004-03-03 15:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 18:42 Mariusz Mazur
2004-02-29 20:19 ` H. Peter Anvin
2004-02-29 20:30 ` Mariusz Mazur
2004-02-29 21:03 ` H. Peter Anvin
2004-02-29 21:21 ` Mariusz Mazur
2004-02-29 21:33 ` Måns Rullgård
2004-03-01 14:42 ` Chris Friesen
2004-03-01 18:10 ` Krzysztof Halasa
2004-03-03 12:49 ` Måns Rullgård
2004-03-03 15:22 ` Sam Ravnborg [this message]
2004-03-03 16:49 ` Krzysztof Halasa
2004-03-04 16:50 ` Jeff Garzik
2004-03-04 18:49 ` [Linuxabi] " H. Peter Anvin
2004-03-04 4:43 ` [Linuxabi] " H. Peter Anvin
2004-03-03 18:08 ` [ANNOUNCE] " Mariusz Mazur
2004-03-03 19:20 ` Grzegorz Kulewski
2004-03-04 14:13 ` Krzysztof Halasa
2004-03-04 20:49 ` Mariusz Mazur
2004-03-04 21:27 ` Chris Friesen
2004-03-04 22:52 ` Mariusz Mazur
2004-03-04 23:32 ` Chris Friesen
2004-03-05 17:02 ` Krzysztof Halasa
2004-03-05 23:44 ` Grzegorz Kulewski
2004-03-06 22:30 ` Krzysztof Halasa
2004-03-07 1:15 ` Paul Jackson
2004-03-07 19:00 ` Krzysztof Halasa
2004-03-08 1:28 ` Paul Jackson
2004-03-08 15:03 ` Krzysztof Halasa
2004-03-08 15:37 ` Chris Friesen
2004-03-08 20:27 ` Krzysztof Halasa
2004-02-29 21:25 ` Benjamin Herrenschmidt
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=20040303152213.GA2148@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=cfriesen@nortelnetworks.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxabi@zytor.com \
--cc=mru@kth.se \
/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
all inboxes | Powered by JetHome®