From: Christoph Hellwig <hch@lst.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Werner Almesberger <wa@almesberger.net>,
hch@lst.de, davem@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove dead tcp exports
Date: Tue, 26 Oct 2004 11:36:53 +0200 [thread overview]
Message-ID: <20041026093653.GA22059@lst.de> (raw)
In-Reply-To: <1098765665.9404.5.camel@krustophenia.net>
On Tue, Oct 26, 2004 at 12:41:05AM -0400, Lee Revell wrote:
> On Mon, 2004-10-25 at 20:41 -0700, David S. Miller wrote:
> > On Tue, 26 Oct 2004 00:07:10 -0300
> > Werner Almesberger <wa@almesberger.net> wrote:
> >
> > > Wheee, you had me scared for a moment. But indeed, not even tcpcp
> > > (tcpcp.sf.net) uses any of these. But I kind of wonder how you
> > > determine they're "dead" ?
> >
> > There are scripts which build everything as possible as modules
> > then greps the symbol tables of the object files to see which
> > symbols exported by the kernel are actually used.
>
> Is this really a compelling reason to remove them? For example ALSA
> provides an API for driver writers, just because a certain function
> happens not to be used by any does not mean is never will be or that it
> should not.
I've excluded functions where I thoug hthe API makes sense. Of course
I don't know all code in the kernel nor do I always make the right
decision, so I ask the maintainers for their opinion.
prev parent reply other threads:[~2004-10-26 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-24 13:43 [PATCH] remove dead tcp exports Christoph Hellwig
2004-10-26 3:07 ` Werner Almesberger
2004-10-26 3:41 ` David S. Miller
2004-10-26 3:55 ` Werner Almesberger
2004-10-26 4:41 ` Lee Revell
2004-10-26 4:52 ` David S. Miller
2004-10-26 5:43 ` Lee Revell
2004-10-26 8:40 ` Arjan van de Ven
2004-10-26 9:36 ` Christoph Hellwig [this message]
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=20041026093653.GA22059@lst.de \
--to=hch@lst.de \
--cc=davem@davemloft.net \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=wa@almesberger.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.