From: Krzysztof Halasa <khc@pm.waw.pl>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Mariusz Mazur <mmazur@kernel.pl>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] linux-libc-headers 2.6.7.0
Date: Thu, 24 Jun 2004 18:43:56 +0200 [thread overview]
Message-ID: <m3n02s9a9f.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <40DA0F7D.60606@pobox.com> (Jeff Garzik's message of "Wed, 23 Jun 2004 19:17:17 -0400")
Jeff Garzik <jgarzik@pobox.com> writes:
> HPA suggested include/abi and I don't think anyone objected.
>
> But that's most likely a 2.7 project :(
I think we should start with (and it doesn't have to wait for 2.7):
/usr/include/abi -> linux/include/abi
/usr/include/linux -> abi (obsolete, to be removed with 2.8)
Appropriate $ARCH + generic dirs (names?).
in the kernel:
mkdir linux/include/abi (and appropriate $ARCH + generic dirs - names?)
for f in all-user-space-header-names; do
copy << EOF >> linux/include/abi/$f
#ifndef __ABI_HEADER_H
#define __ABI_HEADER_H
#ifdef __KERNEL__
#include <linux/header.h>
#else
#include <linux-internal/header.h>
#endif
#endif
I above scheme should give us a) source compatibility with both kernel
and userland files, b) smooth transition without a single 50 MB patch,
c) allows each maintainer to move/clean "her/his" headers independently.
After a header file is "cleaned" it would look like:
#ifndef __ABI_HEADER_H
#define __ABI_HEADER_H
#include <abi/required_headers.h>
... actual ABI definitions
#endif
-------
#ifndef __LINUX_HEADER_H
#define __LINUX_HEADER_H
#include <abi/required_headers.h>
#include <linux/required_headers.h>
... kernel-only stuff
#endif
--
Krzysztof Halasa, B*FH
next prev parent reply other threads:[~2004-06-24 19:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 22:20 Mariusz Mazur
2004-06-23 22:54 ` Chris Friesen
2004-06-23 23:02 ` Mariusz Mazur
2004-06-23 23:48 ` Chris Friesen
2004-06-24 5:58 ` Greg KH
2004-06-24 9:18 ` Jeff Garzik
2004-06-24 11:02 ` Mariusz Mazur
2004-06-24 13:53 ` Andries Brouwer
2004-06-24 19:29 ` Sam Ravnborg
2004-06-23 23:17 ` Jeff Garzik
2004-06-23 23:30 ` Mariusz Mazur
2004-06-24 16:43 ` Krzysztof Halasa [this message]
2004-06-25 9:25 ` Martin Waitz
2004-06-25 10:02 ` Andries Brouwer
2004-06-25 11:33 ` Rob Landley
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=m3n02s9a9f.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmazur@kernel.pl \
/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®