From: Arne Caspari <arne@datafloater.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Arne Caspari <arnem@informatik.uni-bremen.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ben Collins <bcollins@debian.org>,
linux1394-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] ieee1394_core.c: remove unneeded EXPORT_SYMBOL's
Date: Tue, 21 Dec 2004 13:49:56 +0100 [thread overview]
Message-ID: <41C81BF4.9070602@datafloater.de> (raw)
In-Reply-To: <20041221120012.GC5217@stusta.de>
Adrian Bunk schrieb:
>On Tue, Dec 21, 2004 at 09:33:45AM +0100, Arne Caspari wrote:
>
>
>>...
>>I would take it like in a library: The API should not change between
>>minor versions - likewise it should be stable in the kernel among all
>>2.6.x versions. If it changes to version 2.7.x or 2.8.x it would be OK
>>since we could release a driver for a 2.8.x tree then.
>>
>>
>
>The current development model published by Linus Torvalds and
>Andrew Morton is that there will be no 2.7.x in the forseeable future,
>but instead the changes that would go into a 2.7 series go into the 2.6
>series...
>
>
To make a long decision short:
There is no stable kernel API that an external developer can rely on?
And this is by intent: The only way for a vendor to write a driver for
Linux is to submit it to the kernel tree?
/Arne
next prev parent reply other threads:[~2004-12-21 12:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 1:53 [2.6 patch] ieee1394_core.c: remove unneeded EXPORT_SYMBOL's Adrian Bunk
2004-12-20 2:10 ` Dan Dennedy
2004-12-20 2:25 ` Adrian Bunk
2004-12-20 2:42 ` Lee Revell
2004-12-20 4:27 ` Dan Dennedy
2004-12-20 22:53 ` Adrian Bunk
2004-12-20 22:58 ` Lee Revell
2004-12-20 23:02 ` Adrian Bunk
2004-12-20 23:21 ` Lee Revell
2004-12-21 0:40 ` Alan Cox
2004-12-21 17:17 ` Greg KH
2004-12-21 17:20 ` Lee Revell
2004-12-21 17:27 ` Greg KH
2004-12-21 22:19 ` Theodore Ts'o
2004-12-22 14:08 ` Alan Cox
2004-12-20 9:01 ` Arne Caspari
2004-12-20 12:15 ` Arjan van de Ven
2004-12-20 13:20 ` Arne Caspari
2004-12-20 14:35 ` Alan Cox
2004-12-22 8:29 ` Arjan van de Ven
2004-12-22 8:57 ` Stefan Richter
2004-12-22 12:01 ` Christoph Hellwig
2004-12-22 12:21 ` Arne Caspari
2004-12-22 16:04 ` Stefan Richter
2004-12-20 14:39 ` Ben Collins
2004-12-20 15:15 ` Alan Cox
2004-12-20 15:46 ` Ben Collins
2004-12-20 20:15 ` Alan Cox
2004-12-21 8:33 ` Arne Caspari
2004-12-21 12:00 ` Adrian Bunk
2004-12-21 12:49 ` Arne Caspari [this message]
2004-12-21 17:15 ` Greg KH
2004-12-21 18:51 ` Arne Caspari
2004-12-21 18:58 ` Greg KH
2004-12-20 17:51 ` Adrian Bunk
2004-12-20 21:05 ` Lee Revell
2004-12-20 21:49 ` girish wadhwani
2004-12-21 8:37 ` Arne Caspari
2004-12-21 9:06 ` Bernard Leach
2004-12-21 23:35 ` Pieter Palmers
2004-12-22 0:56 ` Lee Revell
2004-12-21 0:42 ` updated: " Adrian Bunk
2004-12-21 8:46 ` Arne Caspari
2004-12-21 17:13 ` Greg KH
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=41C81BF4.9070602@datafloater.de \
--to=arne@datafloater.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnem@informatik.uni-bremen.de \
--cc=bcollins@debian.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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.