From: Douglas Gilbert <dougg@torque.net>
To: Andi Kleen <ak@suse.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Removing BROKEN scsi drivers
Date: Thu, 06 Oct 2005 08:36:27 +1000 [thread overview]
Message-ID: <4344556B.3030700@torque.net> (raw)
In-Reply-To: <200510051314.33411.ak@suse.de>
Andi Kleen wrote:
> In 2.6.14rc3:
>
> linux/drivers/scsi> grep -c BROKEN Kconfig
> 11
>
> There are a lot of SCSI drivers who have been marked BROKEN forever. Or at
> least for all of 2.6 and one would expect if there are users left they would
> have fixed them by now. Would it make sense to remove them?
>
> In particular:
>
> SCSI_ADVANSYS - vendor went out of market afaik. Probably not many left.
Andi,
My advansys controllers work fine in lk 2.6 .
Advansys itself (or its SCSI HBA line) was onsold
several times. I'm not sure if they are still
available (the last ones for sale that I noticed
were for SCSI (SPI-based) scanners). When lk 2.5
development changes broke the drivers, patches came
in from several contributors to fix them (usually
the minimum required). I believe they are still
out there, probably in decreasing numbers (e.g.
I decommissioned a server using one last week).
It's nice (albeit aging) hardware whose reliability
exceeds that of a few other HBA manufacturers'
products I could name.
So whoever marked the advansys driver as broken
was making some political statement IMO. If it
ain't broken, it shouldn't be marked as BROKEN.
If the kernel source was split up at some stage (rather
than one big source tarball), it may be appropriate
to put the advansys driver in with the second tier
(looking for a better term than "legacy") drivers.
Doug Gilbert
next prev parent reply other threads:[~2005-10-05 22:35 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 11:14 Removing BROKEN scsi drivers Andi Kleen
2005-10-05 11:22 ` Arjan van de Ven
2005-10-05 11:31 ` Matthew Wilcox
2005-10-05 11:39 ` Christoph Hellwig
2005-10-05 12:32 ` Richard Hirst
2005-10-05 13:30 ` Kars de Jong
2005-10-05 14:00 ` Richard Hirst
2005-10-05 14:03 ` James Bottomley
2005-10-05 14:35 ` Rolf Eike Beer
2005-10-07 8:27 ` Geert Uytterhoeven
2005-10-07 13:42 ` Richard Hirst
2005-10-07 13:53 ` Kars de Jong
2005-11-15 9:51 ` Christoph Hellwig
2005-11-15 10:17 ` Ingo Juergensmann
2005-11-15 10:30 ` Christoph Hellwig
2005-11-15 11:32 ` Richard Hirst
2005-11-15 12:08 ` Roman Zippel
2005-11-15 12:11 ` Kars de Jong
2005-11-15 13:05 ` Matthew Wilcox
2005-11-22 8:36 ` Christoph Hellwig
2005-11-22 21:43 ` Kars de Jong
2005-11-22 22:20 ` Matthew Wilcox
2005-11-27 16:47 ` James Bottomley
2005-11-29 22:24 ` James Bottomley
2005-11-30 8:31 ` Kars de Jong
2005-11-30 8:45 ` Ingo Juergensmann
2005-12-01 20:43 ` Kars de Jong
2005-12-01 20:47 ` James Bottomley
2005-12-01 23:29 ` Richard Hirst
2005-12-02 15:03 ` Ingo Juergensmann
2005-12-07 21:25 ` Ingo Juergensmann
2006-07-07 12:44 ` Christoph Hellwig
2006-07-09 11:16 ` Richard Hirst
2006-07-09 11:25 ` Kars de Jong
2006-10-30 11:13 ` Christoph Hellwig
2006-10-30 12:34 ` Kars de Jong
2006-10-31 21:47 ` [RFC PATCH] m68k: switch to 53c700 driver Kars de Jong
2006-11-02 21:34 ` Geert Uytterhoeven
2006-12-17 22:28 ` James Bottomley
2006-12-18 9:34 ` Geert Uytterhoeven
2006-12-19 3:09 ` Al Viro
2006-12-22 21:21 ` Kars de Jong
2007-04-29 21:43 ` Christoph Hellwig
2005-10-05 11:43 ` Removing BROKEN scsi drivers Christoph Hellwig
2005-10-05 22:36 ` Douglas Gilbert [this message]
2005-10-06 10:23 ` Andi Kleen
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=4344556B.3030700@torque.net \
--to=dougg@torque.net \
--cc=ak@suse.de \
--cc=linux-scsi@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 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.