From: Krzysztof Halasa <khc@pm.waw.pl>
To: Adrian Bunk <bunk@stusta.de>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Andrew Morton <akpm@osdl.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove the broken SCSI_SEAGATE driver
Date: Fri, 15 Dec 2006 14:34:13 +0100 [thread overview]
Message-ID: <m3wt4tp9ka.fsf@defiant.localdomain> (raw)
In-Reply-To: <20061213000902.GD28443@stusta.de> (Adrian Bunk's message of "Wed, 13 Dec 2006 01:09:02 +0100")
Adrian Bunk <bunk@stusta.de> writes:
> There must have been a compile error that has since been fixed, but I
> don't remember the details of this specific driver and I don't have
> such old compile logs anymore.
I wonder if we could gather some usage statistics, especially WRT
really old hardware.
Perhaps we could invent some MODULE_WARN_OBSOLETE thing which would
warn users about their drivers being removed in +6m (or maybe +12m),
unless they let us know at http://qwe or mailto:ads?
I find it really hard to believe there are still users of things like
CDU-31A CDs, XT MFM disk controllers, or NCR5380 SCSI host adapters
(especially the real ones, not DOMEX etc. clones bundled with scanner
just ~ 10 years ago).
--
Krzysztof Halasa
next prev parent reply other threads:[~2006-12-15 14:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 16:22 [2.6 patch] remove the broken SCSI_SEAGATE driver Adrian Bunk
2006-12-12 23:31 ` James Bottomley
2006-12-13 0:09 ` Adrian Bunk
2006-12-15 13:34 ` Krzysztof Halasa [this message]
2006-12-15 14:05 ` Oliver Neukum
2006-12-15 16:00 ` James Bottomley
2006-12-17 20:03 ` Krzysztof Halasa
2006-12-17 20:22 ` James Bottomley
2006-12-17 21:18 ` Krzysztof Halasa
2006-12-18 8:47 ` Arjan van de Ven
2006-12-18 13:48 ` Krzysztof Halasa
2006-12-18 15:20 ` Arjan van de Ven
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=m3wt4tp9ka.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--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.