From: James Bottomley <James.Bottomley@SteelEye.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Adrian Bunk <bunk@stusta.de>, 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: Sun, 17 Dec 2006 14:22:46 -0600 [thread overview]
Message-ID: <1166386966.9647.20.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <m3ac1mb88s.fsf@defiant.localdomain>
On Sun, 2006-12-17 at 21:03 +0100, Krzysztof Halasa wrote:
> James Bottomley <James.Bottomley@SteelEye.com> writes:
>
> > I really don't see a need to declare drivers obsolete unless they bitrot
> > to the point they're demonstrably useless and no-one wants to step up to
> > fix them, which is what the BROKEN flag is for.
>
> How do you know if the driver is broken? Especially if it still
> compiles?
>
> Some of these things are 20 years old.
One of the touted benefits of Linux is that we run on old hardware.
Unless the driver is demonstrably wrong (and they do become so as the
APIs evolve) or it fails to compile because of bitrotting, there's no
real urgency to remove it, is there?
The reverse (how do you know if someone's still using the driver) is
equally hard to determine.
James
next prev parent reply other threads:[~2006-12-17 20:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 16:22 Adrian Bunk
2006-12-12 23:31 ` James Bottomley
2006-12-13 0:09 ` Adrian Bunk
2006-12-15 13:34 ` Krzysztof Halasa
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 [this message]
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=1166386966.9647.20.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=khc@pm.waw.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®