From: "Russell, Nathaniel" <reddog83@chartermi.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trivial patch for 2.4.20-pre1 8139too.c driver (fwd)
Date: Tue, 06 Aug 2002 13:41:23 -0400 [thread overview]
Message-ID: <web-46527136@back1.chartermi.net> (raw)
In-Reply-To: <3D4FF809.4040106@mandrakesoft.com>
My i ask what the sense is to not remove the dead code if
all we are trying to do is stablize the 2.4x kernel series
and not add extra code or change around the drivers for
perticular hardware. The code is not used anymore so why
keep it in the 2.4x series. The code can stay in the 2.5x
series no problem because there we can change drivers
rewrite hardware protocalls and tthings like that.
Marcelo Tosatti wrote:
>
>---------- Forwarded message ----------
>Date: Tue, 6 Aug 2002 00:15:21 +0000
>From: Nathaniel Russell <reddog83@chartermi.net>
>To: marcelo@conectiva.com.br
>Cc: alan@lxorguk.ukuu.org.uk
>Subject: [PATCH] trivial patch for 2.4.20-pre1 8139too.c
driver
>
>This patch removes unneeded code for the Realtek driver
this patch does not
>harm the performance of the driver at all it just removes
dead code
>
>
>------------------------------------------------------------------------
>
>diff -urN linux-2.4/drivers/net/8139too.c.tmp
linux/drivers/net/8139too.c
>--- linux-2.4/drivers/net/8139too.c.tmp Mon Aug 5
18:06:03 2002
>+++ linux/drivers/net/8139.c Tue Aug 6 00:09:20 2002
>@@ -211,7 +211,6 @@
> RTL8139 = 0,
> RTL8139_CB,
> SMC1211TX,
>- /*MPX5030,*/
> DELTA8139,
> ADDTRON8139,
> DFE538TX,
[...]
Please -do not- apply this patch. This "dead code" exists
for comment purposes, and also is a placeholder for
future, better support for this chip.
Jeff
next parent reply other threads:[~2002-08-06 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D4FF809.4040106@mandrakesoft.com>
2002-08-06 17:41 ` Russell, Nathaniel [this message]
2002-08-06 17:44 ` [PATCH] trivial patch for 2.4.20-pre1 8139too.c driver (fwd) Jeff Garzik
2002-08-06 19:28 ` Russell, Nathaniel
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=web-46527136@back1.chartermi.net \
--to=reddog83@chartermi.net \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
/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