From: "David S. Miller" <davem@redhat.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: tmattox@gmail.com, hadi@cyberus.ca, netdev@oss.sgi.com
Subject: Re: [RFC,PATCH] fastroute dead code...
Date: Fri, 30 Jul 2004 13:10:04 -0700 [thread overview]
Message-ID: <20040730131004.2be1274d.davem@redhat.com> (raw)
In-Reply-To: <20040730193515.GA11365@havoc.gtf.org>
On Fri, 30 Jul 2004 15:35:15 -0400
Jeff Garzik <jgarzik@pobox.com> wrote:
> It is dead code, as-is, in the kernel. It would require patches to
> actually work at all.
>
> It is impossible that fastrouting is being actively used, without patches.
I totally agree. And people can always resurrect it from the
repository history or an old tarball if they wish.
I think it should be killed entirely, and that's what I'm going
to do.
next prev parent reply other threads:[~2004-07-30 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 6:03 [RFC,PATCH] fastroute dead code Jeff Garzik
2004-07-30 19:29 ` Tim Mattox
2004-07-30 19:35 ` Jeff Garzik
2004-07-30 20:10 ` David S. Miller [this message]
2004-07-30 20:27 ` jamal
2004-07-30 21:11 ` Jeff Garzik
2004-08-02 11:45 ` Andi Kleen
2004-07-30 20:29 ` Tim Mattox
2004-07-30 21:08 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-07-30 20:31 Manish Lachwani
2004-07-30 21:05 ` jamal
2004-08-02 15:26 ` Kumar Gala
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=20040730131004.2be1274d.davem@redhat.com \
--to=davem@redhat.com \
--cc=hadi@cyberus.ca \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=tmattox@gmail.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;
as well as URLs for NNTP newsgroup(s).