From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Proper way to release binary driver?
Date: Mon, 9 Apr 2001 13:11:12 +0000 (UTC) [thread overview]
Message-ID: <9ascdh$rh3$1@forge.intermeta.de> (raw)
In-Reply-To: <3ACDE5C5.CEB65D4A@raleigh.ibm.com> <E14lnvn-0007AS-00@the-village.bc.nu>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>> We had hoped that MODVERSIONS would allow us to provide a single (or at
>> most a few) binary driver. Kernels with even minor version numbers are
>> supposed to be stable (even if they are buggy) ie. not have wildly
>> changing kernel interfaces.
>They have a stable API. THe ABI thing is an irrelevance to free software.
>avoiding the ABI compatibility mess is one of the great things free
>software lets you do.
^free^open source
Ciao
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
next prev parent reply other threads:[~2001-04-09 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 10:58 Proper way to release binary-only driver? Miller, Brendan
2001-04-05 11:50 ` Eric W. Biederman
2001-04-06 15:50 ` Proper way to release binary driver? Christopher Turcksin
2001-04-06 16:09 ` Joel Jaeggli
2001-04-06 16:22 ` J . A . Magallon
2001-04-07 1:24 ` How to build modules outside the kernel tree? [Was: Proper way to release binary driver?] Eric W. Biederman
2001-04-08 13:10 ` Jamie Lokier
2001-04-07 8:18 ` Proper way to release binary driver? Alan Cox
2001-04-09 13:11 ` Henning P. Schmiedehausen [this message]
2001-04-07 11:06 ` Christopher Turcksin
2001-04-06 5:33 ` Proper way to release binary-only driver? Alan Cox
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='9ascdh$rh3$1@forge.intermeta.de' \
--to=hps@intermeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.