From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Russell, Nathaniel" <reddog83@chartermi.net>
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:44:17 -0400 [thread overview]
Message-ID: <3D500AF1.9050901@mandrakesoft.com> (raw)
In-Reply-To: web-46527136@back1.chartermi.net
Russell, Nathaniel wrote:
> 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.
...because I maintain the driver, and want to keep that code around as a
note to myself.
Jeff
next prev parent reply other threads:[~2002-08-06 17:40 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 ` [PATCH] trivial patch for 2.4.20-pre1 8139too.c driver (fwd) Russell, Nathaniel
2002-08-06 17:44 ` Jeff Garzik [this message]
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=3D500AF1.9050901@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reddog83@chartermi.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