From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 future
Date: Tue, 2 Dec 2003 19:45:13 +0100 [thread overview]
Message-ID: <20031202184513.GU16507@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0312020956120.1519@home.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
On Tue, 2003-12-02 10:04:24 -0800, Linus Torvalds <torvalds@osdl.org>
wrote in message <Pine.LNX.4.58.0312020956120.1519@home.osdl.org>:
> On Tue, 2 Dec 2003, Jan-Benedict Glaw wrote:
> >
> > On Tue, 2003-12-02 02:23:55 +0000, snpe <snpe@snpe.co.yu>
> > wrote in message <200312020223.55505.snpe@snpe.co.yu>:
> > > Is there linux-abi for 2.6 kernel ?
> >
> > Nobody really cares about ABI (at least, not enough to keep one stable)
> > while there's a good API. That requires sources, though, but that's a
> > good thing...
> You are, however, correct when it comes to internal kernel interfaces: we
> care not at all about ABI's, and even API's are fluid and are freely
> changed if there is a real technical reason for it. But that is only true
> for the internal kernel stuff (where source is obviously a requirement
> anyway).
Whenever The ABI Question (TM) comes up, it seems to be about claiming a
(binary compatible) interface - mostly for modules. But I think it's
widely accepted that there isn't much work done to have these truly (sp?)
binary compatible (eg. UP/SMP spinlocks et al.).
Of course, we want to have a somewhat stable interface for libc (->
userspace), but some struct (fb_info, ...) doesn't need to be binary
compatible - as long as a driver (given to be in source) still works
cleanly with it:)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-02 18:45 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 14:25 Linux 2.4 future Marcelo Tosatti
2003-12-01 15:04 ` Ian Kent
2003-12-01 15:33 ` Christoph Hellwig
2003-12-01 21:36 ` Peter C. Norton
2003-12-01 23:54 ` Arjan van de Ven
2003-12-02 1:11 ` Ian Kent
2003-12-02 20:13 ` Peter C. Norton
2003-12-02 20:10 ` Peter C. Norton
2003-12-02 20:18 ` Arjan van de Ven
2003-12-02 20:46 ` Peter C. Norton
2003-12-03 1:23 ` Ian Kent
2003-12-03 10:36 ` Matthias Andree
2003-12-03 14:49 ` Ian Kent
2003-12-03 15:00 ` Matthias Andree
2003-12-04 6:24 ` Ian Kent
2003-12-02 21:56 ` Bryan Whitehead
2003-12-02 8:17 ` Christoph Hellwig
2003-12-02 1:09 ` Ian Kent
2003-12-02 2:23 ` snpe
2003-12-02 6:39 ` Jan-Benedict Glaw
2003-12-02 18:04 ` Linus Torvalds
2003-12-02 18:45 ` Jan-Benedict Glaw [this message]
2003-12-02 19:09 ` Linus Torvalds
2003-12-02 19:13 ` Jan-Benedict Glaw
2003-12-02 19:39 ` Gene Heskett
2003-12-02 20:13 ` Jeff Garzik
2003-12-02 20:32 ` Stephan von Krawczynski
2003-12-02 21:48 ` Gene Heskett
2003-12-02 21:56 ` Linus Torvalds
2003-12-03 2:36 ` Harald Arnesen
2003-12-03 9:21 ` Helge Hafting
2003-12-02 19:59 ` snpe
2003-12-02 22:30 ` Mike Fedyk
2003-12-02 22:43 ` Arnaldo Carvalho de Melo
2003-12-03 14:08 ` snpe
2003-12-03 13:26 ` Christoph Hellwig
2003-12-02 8:18 ` Christoph Hellwig
2003-12-01 15:26 ` Norberto Bensa
2003-12-01 23:30 ` 2.6 security patches merged? was: " Mike Fedyk
2003-12-02 0:06 ` Chris Wright
2003-12-02 0:58 ` Måns Rullgård
2003-12-02 1:56 ` Chris Wright
2003-12-02 11:55 ` Marcelo Tosatti
2003-12-02 9:00 ` Matthias Andree
2003-12-02 11:54 ` Ionut Georgescu
2003-12-02 12:03 ` Arnaldo Carvalho de Melo
2003-12-02 13:13 ` Ionut Georgescu
2003-12-02 13:38 ` Ed Sweetman
2003-12-02 14:12 ` Arnaldo Carvalho de Melo
2003-12-02 16:01 ` Ionut Georgescu
2003-12-02 16:08 ` Jeff Garzik
2003-12-02 18:20 ` John Bradford
2003-12-02 20:19 ` Ville Herva
2003-12-02 21:40 ` Chris Wright
2003-12-02 20:09 ` Stephan von Krawczynski
2003-12-02 20:24 ` Arnaldo Carvalho de Melo
2003-12-02 20:45 ` Stephan von Krawczynski
2003-12-02 21:03 ` Arnaldo Carvalho de Melo
[not found] ` <Pine.LNX.4.58.0312021402360.17892@moje.vabo.cz>
[not found] ` <20031202131512.GU13388@conectiva.com.br>
[not found] ` <Pine.LNX.4.58.0312021433360.8417@moje.vabo.cz>
[not found] ` <20031202135423.GB13388@conectiva.com.br>
2003-12-02 20:21 ` Tomas Konir
2003-12-02 18:53 ` Mike Fedyk
2003-12-02 19:06 ` Valdis.Kletnieks
2003-12-02 23:13 ` Jose Luis Domingo Lopez
2003-12-03 18:22 ` bill davidsen
2003-12-04 1:24 ` jw schultz
2003-12-04 1:47 ` Mike Fedyk
2003-12-04 3:45 ` Tim Connors
2003-12-04 5:41 ` Willy Tarreau
2003-12-05 0:14 ` jw schultz
2003-12-01 15:56 ` Marcelo Tosatti
2003-12-01 21:02 ` David S. Miller
2003-12-03 21:26 ` Jan Rychter
2003-12-03 20:51 ` Jeff Garzik
2003-12-03 21:14 ` Willy Tarreau
2003-12-05 15:33 ` John Jasen
2003-12-05 22:23 ` Mike Fedyk
2003-12-06 15:49 ` Max Valdez
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=20031202184513.GU16507@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.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).