From: Ondrej Zary <linux@rainbow-software.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org, Miroslav Zagorac <zaga@fly.cc.fer.hr>,
Dario Ballabio <ballabio_dario@emc.com>
Subject: Re: RFC: should we deprecate unmaintained isa-only drivers?
Date: Tue, 6 Jan 2015 23:27:28 +0100 [thread overview]
Message-ID: <201501062327.28830.linux@rainbow-software.org> (raw)
In-Reply-To: <20141230160616.GA29149@infradead.org>
On Tuesday 30 December 2014 17:06:16 Christoph Hellwig wrote:
> We've got a few very old, isa-only SCSI HBA drivers in the tree. Of
> those only one (aha152x) sas significant maintaince since the dawn
> of git, all others only saw global / automatic updates. 4 of those
> are fairly trivial wrappers aroudn the NCR538 core, so I don't mind
> keeping them:
>
> - dtc
> - g_NCR5380
> - pas16
> - t128
>
> but I'd love to know if anyone is actually using the other drivers:
>
> - wd7000
> - aha1542
> - in2000
> - NCR53c406
> - sym53c416
> - u14-34f
> - ultrastor
>
> note that the last two even drive the same hardware. There is
> significant cruft in all these, so dropping them would help
> further maintainance of the SCSI midlayer.
I think I have a AHA-1542B ISA card so I can fix the aha1542 driver.
--
Ondrej Zary
next prev parent reply other threads:[~2015-01-06 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 16:06 RFC: should we deprecate unmaintained isa-only drivers? Christoph Hellwig
2015-01-06 22:27 ` Ondrej Zary [this message]
2015-01-07 14:34 ` Christoph Hellwig
2015-01-09 19:44 ` Ondrej Zary
2015-03-25 20:52 ` Ondrej Zary
2015-04-06 15:22 ` Christoph Hellwig
2016-09-11 17:01 ` Christoph Hellwig
2016-09-11 17:33 ` Ondrej Zary
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=201501062327.28830.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=ballabio_dario@emc.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=zaga@fly.cc.fer.hr \
/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).