From: Lee Revell <rlrevell@joe-job.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Dan Dennedy <dan@dennedy.org>, Ben Collins <bcollins@debian.org>,
Linux1394-Devel <linux1394-devel@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] ieee1394_core.c: remove unneeded EXPORT_SYMBOL's
Date: Sun, 19 Dec 2004 21:42:14 -0500 [thread overview]
Message-ID: <1103510535.1252.18.camel@krustophenia.net> (raw)
In-Reply-To: <20041220022503.GT21288@stusta.de>
On Mon, 2004-12-20 at 03:25 +0100, Adrian Bunk wrote:
> On Sun, Dec 19, 2004 at 09:10:10PM -0500, Dan Dennedy wrote:
> > On Mon, 2004-12-20 at 02:53 +0100, Adrian Bunk wrote:
> > > The patch below removes 41 unneeded EXPORT_SYMBOL's.
> >
> > Unneeded according to whom, just you? These functions are part of an
> > API. How do I know someone is not using these in a custom ieee1394
> > kernel module in some industrial or research setting or something new
> > under development to be contributed to linux1394 project?
>
> If someone uses some of them in code to be contributed to the linux1394
> project, re-adding the EXPORT_SYMBOL's in question is trivial.
>
> If someone uses some of them in a custom setting, re-adding them is
> trivial, too.
>
> If the only user of one or more of these EXPORT_SYMBOL's was a non-free
> module, it's kernel policy that the EXPORT_SYMBOL's in question have to
> be removed.
What do you tell a vendor who wants to write a driver for their device?
"OK, about half the functions you need are in the kernel, the other half
you have to port from this old kernel because we removed them. Maybe we
will put them back if we really like your driver"?
Lee
next prev parent reply other threads:[~2004-12-20 2:42 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 [this message]
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
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=1103510535.1252.18.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=bcollins@debian.org \
--cc=bunk@stusta.de \
--cc=dan@dennedy.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox