From: Bernard Leach <leachbj@bouncycastle.org>
To: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Cc: girish wadhwani <girish.wadh@gmail.com>,
Lee Revell <rlrevell@joe-job.com>, Adrian Bunk <bunk@stusta.de>,
bcollins@debian.org,
Arne Caspari <arnem@informatik.uni-bremen.de>
Subject: Re: [2.6 patch] ieee1394_core.c: remove unneeded EXPORT_SYMBOL's
Date: Tue, 21 Dec 2004 10:06:10 +0100 [thread overview]
Message-ID: <1103619970.8788.12.camel@localhost> (raw)
In-Reply-To: <41C7E0D4.6010207@informatik.uni-bremen.de>
The basis for removal of these exports was an alledged policy that
states unless there is at least one known opensource (GPL?) driver that
uses them they should not exist. (I hope that paraphrase captured the
essence of the previous statements).
If this policy is as stated then its clearly short sighted. If the
kernel is simply (the kernel and) the set of interfaces that support the
_existing_ drivers then that is all it will ever be. I'm not saying
that is impossible for a driver writer to construct new interfaces that
their driver will require but I would suggest that in most cases this is
an unreasonable requirement.
APIs are a mechanism to export functionality from a particular
black-box, does it make sense that the constructor of that black-box
defines this API or some poor sod who has been given that black box on a
Friday afternoon and asked to deliver a driver on Monday?
Anyhow I think Ben has made it quite clear that this API exists for a
reason.
My point would be that waving some arbitrary policy around like the holy
grail does nothing to build a better kernel.
cheers,
bern.
next prev parent reply other threads:[~2004-12-21 9:12 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
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 [this message]
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=1103619970.8788.12.camel@localhost \
--to=leachbj@bouncycastle.org \
--cc=arnem@informatik.uni-bremen.de \
--cc=bcollins@debian.org \
--cc=bunk@stusta.de \
--cc=girish.wadh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=rlrevell@joe-job.com \
/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