From: Dan Dennedy <dan@dennedy.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] drivers/ieee1394/: remove unneeded EXPORT_SYMBOL's
Date: Wed, 20 Apr 2005 16:32:24 -0400 [thread overview]
Message-ID: <1114029144.5085.20.camel@kino.dennedy.org> (raw)
In-Reply-To: <426683E9.4080708@s5r6.in-berlin.de>
On Wed, 2005-04-20 at 18:31 +0200, Stefan Richter wrote:
> Arjan van de Ven wrote:
> > On Wed, 2005-04-20 at 00:00 +0200, Stefan Richter wrote:
> >>There are users (though not in "the" kernel at the moment)
> > nor for the last 5 months... how long will it be ?
>
> Have there been problems with the API during the past 5 months, except
> that several kernel trees are using some parts of the API? (We are
> actually speaking about two APIs of the ieee1394 framework.)
>
> Which problems are solved by this patch? Do they outweigh the problems
> it creates? The latter have been discussed. Dismissing them as Other
> People's Problems does not nullify them.
>
> Where is the agreed-upon, published plan for removal of features in
> ieee1394?
Of course, there is none. In an unofficial capacity, there is just the
opinion and votes of the subsystem maintainers, extended team (e.g.,
Stefan and me), and kernel maintainers (Linus, Andrew, and Marcello).
The users are represented by the subsystem maintainers and extended
team. So, Arjan's opinion does not matter except to offer some voice of
reason.
I think I was first to raise objection upon the initial submission some
months back, and then I just observed the dialog. There are technical
merits for removal of the external symbols that I accept. I also accept
that we have no way of maintaining any sort of stable subsystem for
external projects we are not aware of or who are not communicating with
us about their requirements (it goes beyond just a stable interface).
Based upon my experience of several years on this project there is only
one external kernel module project we need to consider because that
developer has been involved and voiced requirements. That is Arne
Caspari's (The Imaging Source) DFG/1394 driver.
I vote to remove external symbols not used by the Linux1394.org modules
or the module at http://sourceforge.net/projects/video-2-1394/
Of course, I may be voted down, but I ask the others to be realistic
about what we are arguing for (i.e. just being defensive?) and consider
the fact that there are valid reasons for their removal.
next prev parent reply other threads:[~2005-04-20 20:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 19:57 Adrian Bunk
2005-04-19 19:13 ` Jody McIntyre
2005-04-19 19:43 ` Arjan van de Ven
2005-04-19 22:00 ` Stefan Richter
2005-04-20 7:26 ` Arjan van de Ven
2005-04-20 16:31 ` Stefan Richter
2005-04-20 16:35 ` Arjan van de Ven
2005-04-20 17:09 ` Stefan Richter
2005-04-20 19:19 ` Arjan van de Ven
2005-04-20 20:32 ` Dan Dennedy [this message]
2005-04-20 20:49 ` Adrian Bunk
2005-04-20 23:43 ` Stefan Richter
2005-04-27 21:11 ` Stefan Richter
2005-04-27 21:38 ` Jesper Juhl
2005-04-27 21:44 ` Adrian Bunk
2005-05-12 22:29 ` Adrian Bunk
2005-05-12 22:30 ` Adrian Bunk
2005-05-12 23:24 ` Stefan Richter
2005-05-13 14:00 ` [2.6 patch] drivers/ieee1394/: schedule unused EXPORT_SYMBOL's for removal Adrian Bunk
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=1114029144.5085.20.camel@kino.dennedy.org \
--to=dan@dennedy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®