From: Adrian Bunk <bunk@stusta.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Simple header cleanups
Date: Thu, 27 Apr 2006 23:37:54 +0200 [thread overview]
Message-ID: <20060427213754.GU3570@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0604262028130.3701@g5.osdl.org>
On Wed, Apr 26, 2006 at 08:31:00PM -0700, Linus Torvalds wrote:
>
> On Thu, 27 Apr 2006, David Woodhouse wrote:
> >
> > Agreed. And distributions and library maintainers _will_ fix them. Are
> > we to deny those people the tools which will help them to keep track of
> > our breakage and submit patches to fix it?
>
> No. As mentioned, as long as the target audience is distributions and
> library maintainers, I definitely think we should do help them as much as
> possible. Our problems have historically been "random people" who have
> /usr/include/linux being the symlink to "kernel source of the day", which
> is an unsupportable situation.
>...
A definition of the kernel <-> userspace ABI is required.
Currently, each distribution does it slightly different.
Currently we might accidentially touch the userspace ABI of the kernel
without even noticing it.
I'd like to do the following:
Create an include/kabi/linux/ with the following properties:
- the goal is that include/kabi/linux an be copied verbatim to
/usr/include/ (by distributions and library maintainers, normal users
should use the copy installed by their distribution in /usr/include/)
- kernel code outside include/ wouldn't notice, since for each ABI
header include/kabi/linux/foo.h there's a header include/linux/foo.h
that does #include <kabi/linux/foo.h>
- moving stuff to kabi/linux can happen incrementially
- once the move is complete, we can announce this as the official ABI
headers
- moving to the kabi/ headers shouldn't cause compile time or
runtime breakages for userspace software [1]
I'd be willing to work on this, but if you have any problems with this
approach, I'd like to understand them
> Linus
cu
Adrian
[1] with the exception of header abuses like the MySQL asm/atomic.h usage
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-04-27 21:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 2:13 Simple header cleanups David Woodhouse
2006-04-27 2:18 ` Linus Torvalds
2006-04-27 2:27 ` Gerrit Huizenga
2006-04-27 2:46 ` Linus Torvalds
2006-04-27 3:00 ` David Woodhouse
2006-04-27 4:32 ` Gerrit Huizenga
2006-04-27 2:37 ` David Woodhouse
2006-04-27 2:59 ` Linus Torvalds
2006-04-27 3:17 ` David Woodhouse
2006-04-27 3:31 ` Linus Torvalds
2006-04-27 3:41 ` David Woodhouse
2006-04-27 7:10 ` Denis Vlasenko
2006-04-27 7:23 ` Arjan van de Ven
2006-04-27 8:49 ` Krzysztof Halasa
2006-04-27 11:03 ` Arnd Bergmann
2006-04-27 21:37 ` Adrian Bunk [this message]
2006-04-27 22:00 ` Linus Torvalds
2006-04-27 23:11 ` David Woodhouse
2006-04-27 23:12 ` Adrian Bunk
2006-04-28 0:01 ` Linus Torvalds
2006-04-28 0:55 ` David Woodhouse
2006-04-28 15:32 ` Jan Engelhardt
2006-04-28 15:37 ` David Woodhouse
2006-04-28 15:59 ` Arjan van de Ven
2006-04-28 16:01 ` Kyle Moffett
2006-04-29 10:33 ` Krzysztof Halasa
2006-05-03 2:53 ` H. Peter Anvin
2006-04-30 9:38 ` Peter Chubb
2006-04-30 9:59 ` David Woodhouse
2006-04-30 21:48 ` Peter Chubb
2006-04-27 15:05 ` David Woodhouse
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=20060427213754.GU3570@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).