public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: 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 01:43:57 -0400	[thread overview]
Message-ID: <1098769437.9404.10.camel@krustophenia.net> (raw)
In-Reply-To: <20041025215216.54b362f9.davem@davemloft.net>

On Mon, 2004-10-25 at 21:52 -0700, David S. Miller wrote:
> On Tue, 26 Oct 2004 00:41:05 -0400
> Lee Revell <rlrevell@joe-job.com> wrote:
> 
> > 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.
> 
> These are actually TCP internals, not a "well defined driver API"
> as ALSA defines.
> 

Yeah but there was also a patch posted that removed a bunch of "dead
exports" from ALSA.  I was wondering in general what the standard is for
distinguishing the two cases.

Lee


  reply	other threads:[~2004-10-26  5:47 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 [this message]
2004-10-26  8:40       ` Arjan van de Ven
2004-10-26  9:36       ` Christoph Hellwig

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=1098769437.9404.10.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=davem@davemloft.net \
    --cc=davem@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox