From: Adrian Bunk <bunk@fs.tum.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: time for some drivers to be removed?
Date: Sun, 27 Jul 2003 17:31:18 +0200 [thread overview]
Message-ID: <20030727153118.GP22218@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0307240817520.19533@localhost.localdomain>
On Thu, Jul 24, 2003 at 08:20:44AM -0400, Robert P. J. Day wrote:
>
> i've mentioned this before, but in a perfect world, should it
> be possible to build a release version of the kernel with
> "make allyesconfig". this is generally not possible, since there's
> always the occasional broken driver that just won't compile.
>
> more to the point, there are drivers that seem to be perpetually
> broken. as an example, the riscom8 driver has been borked for as
> long as i can remember. at some point, shouldn't something like
> this either be fixed or just removed? what's the point of
> perpetually bundling a driver that doesn't even compile?
A first patch is at
http://www.ussg.iu.edu/hypermail/linux/kernel/0306.2/0770.html
I'll send an updated patch against -test2 or -test3.
Ideally, these drivers will be fixed during 2.6 when more people start
using 2.6...
> rday
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-07-27 15:16 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 12:20 time for some drivers to be removed? Robert P. J. Day
2003-07-24 14:58 ` Alan Cox
2003-07-24 15:34 ` Bas Mevissen
2003-07-24 17:32 ` Diego Calleja García
2003-07-24 17:50 ` Robert P. J. Day
2003-07-24 19:16 ` Diego Calleja García
2003-07-24 19:43 ` Robert P. J. Day
2003-07-24 18:02 ` Samuel Flory
2003-07-24 19:07 ` Alan Cox
2003-07-25 10:48 ` Bas Mevissen
2003-07-27 15:31 ` Adrian Bunk [this message]
2003-07-27 15:59 ` David D. Hagood
2003-07-27 16:18 ` Adrian Bunk
2003-07-27 16:40 ` Alan Cox
2003-07-27 17:00 ` Adrian Bunk
2003-07-27 18:45 ` David D. Hagood
2003-07-27 20:40 ` Alan Cox
2003-07-27 20:56 ` Adrian Bunk
2003-07-27 20:56 ` Alan Cox
2003-07-28 2:23 ` Herbert Pötzl
2003-07-29 19:33 ` Adrian Bunk
2003-08-13 20:16 ` Bill Davidsen
2003-08-09 18:04 ` David Woodhouse
2003-08-09 19:36 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2003-07-24 14:43 John Bradford
2003-07-24 19:24 ` Brian Jackson
2003-07-24 18:29 John Bradford
2003-07-24 18:31 ` Robert P. J. Day
2003-07-24 19:31 ` Eli Carter
2003-07-25 10:48 ` Bas Mevissen
2003-07-25 11:10 John Bradford
2003-07-27 16:22 John Bradford
2003-07-28 7:12 linux
2003-08-05 12:42 Mikael Pettersson
2003-08-05 13:03 ` Adrian Bunk
2003-08-05 13:35 ` Mikael Pettersson
2003-08-05 13:48 ` Adrian Bunk
2003-08-05 14:01 ` Mikael Pettersson
2003-08-06 10:06 ` Claus-Justus Heine
2003-08-09 19:40 ` Adrian Bunk
2003-08-05 16:35 ` Alan Cox
2003-08-05 18:47 ` Leopold Gouverneur
2003-08-13 20:55 John Bradford
2003-08-13 20:50 ` Adrian Bunk
2003-08-13 20:55 ` Bill Davidsen
2003-08-14 5:34 John Bradford
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=20030727153118.GP22218@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.