From: William Lee Irwin III <wli@holomorphy.com>
To: Patrick Finnegan <pat@purdueriots.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Dan Kegel <dank@kegel.com>,
john slee <indigoid@higherplane.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why can't Johnny compile?
Date: Fri, 15 Nov 2002 22:15:34 -0800 [thread overview]
Message-ID: <20021116061534.GE23425@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0211160059540.16668-100000@ibm-ps850.purdueriots.com>
On Sat, 16 Nov 2002, Jeff Garzik wrote:
>> If people want to get rivafb or an ancient ISA net driver building
>> again... patches welcome. But I don't think calls for the kernel to
>> compile 100 percent of the drivers is realistic or even reasonable.
>> Some of the APIs, particularly SCSI, are undergoing API stabilization.
[snip]
On Sat, Nov 16, 2002 at 01:04:35AM -0500, Patrick Finnegan wrote:
> Wouldn't it then seem reasonable to remove things from the kernel that
> have been broken for a long time, and no one seems to care enough to fix?
> I know of at least one driver (IOmega Buz v4l) that seems to have fallen
> into disrepair possibly since before 2.4.0, and as far as I know has not
> been repaired since then.
A lot of driver writers probably aren't going to even start updating
until the stable release is released. IIRC there are many vendors etc.
who focus exclusively on stable kernel releases, and who will let their
code (e.g. drivers) bitrot the entire way through the development cycle.
And there is plenty of code that is being updated now for the first
time since 2.0.x, and some arches that haven't merged since before 2.4.0
Bill
next prev parent reply other threads:[~2002-11-16 6:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 5:35 Why can't Johnny compile? Dan Kegel
2002-11-16 5:49 ` Jeff Garzik
2002-11-16 6:04 ` Patrick Finnegan
2002-11-16 6:10 ` Jeff Garzik
2002-11-16 6:15 ` William Lee Irwin III [this message]
2002-11-17 5:34 ` Ralf Baechle
2002-11-16 9:47 ` Kai Henningsen
2002-11-16 14:37 ` Arnaldo Carvalho de Melo
2002-11-16 15:11 ` john slee
2002-11-16 6:23 ` Arnaldo Carvalho de Melo
2002-11-16 19:14 ` Nathan
2002-11-16 21:04 ` Jeff Garzik
2002-11-16 21:37 ` Arnaldo Carvalho de Melo
2002-11-16 21:42 ` Arnaldo Carvalho de Melo
2002-11-16 23:51 ` Alan Cox
2002-11-17 0:09 ` Dan Kegel
2002-11-17 0:08 ` romieu
2002-11-17 3:18 ` Patrick Finnegan
2002-11-17 0:18 ` Nathan
2002-11-17 0:43 ` Alan Cox
2002-11-18 21:02 ` Bill Davidsen
2002-11-18 23:12 ` Alan Cox
2002-11-19 16:30 ` Bill Davidsen
2002-11-19 16:36 ` Jeff Garzik
2002-11-19 17:29 ` Alan Cox
2002-11-19 18:01 ` David G Hamblen
2002-11-19 19:34 ` Alan Cox
2002-11-17 1:34 ` Adam Kropelin
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=20021116061534.GE23425@holomorphy.com \
--to=wli@holomorphy.com \
--cc=dank@kegel.com \
--cc=indigoid@higherplane.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pat@purdueriots.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