From: Andi Kleen <ak@suse.de>
To: linux-scsi@vger.kernel.org
Subject: Removing BROKEN scsi drivers
Date: Wed, 5 Oct 2005 13:14:32 +0200 [thread overview]
Message-ID: <200510051314.33411.ak@suse.de> (raw)
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.
SCSI_CPQFCTS - suboption of another driver, incredibly ugly code defying all
coding standards.
SCSI_EATA_PIO - really old ISA cards. Probably all left over cards are way
over their MTBF by now.
SCSI_SEAGATE - extremly scary code, i doubt there is any such card left
SCSI_MCA_53C9X - BROKEN_ON_SMP only. Ok I guess there are no SMP
Micro Channel systems.
SCSI_QLOGIC_ISP - afaik there is a newer driver for this
SCSI_AMIGA7XX - no maintainer, broken forever
ATARI_SCSI - no maintainer, broken forever
MVME16x_SCSI - no maintainer, broken forever
BVME6000_SCSI - same
SUN3_SCSI - sun3 never worked in mainline anyways
I think they could all go except perhaps the MCA driver. Or at least added
to Documentation/feature-removal-schedule.txt and then removed in a few
months.
-Andi
next reply other threads:[~2005-10-05 11:14 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 11:14 Andi Kleen [this message]
2005-10-05 11:22 ` Removing BROKEN scsi drivers 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
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=200510051314.33411.ak@suse.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).