From: Krzysztof Halasa <khc@pm.waw.pl>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
jeff@garzik.org, linux-ide@vger.kernel.org, alan@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch 3/3] pata: "I do not think it means, what you think it means."
Date: Wed, 05 Mar 2008 17:55:28 +0100 [thread overview]
Message-ID: <m3ejap5cvz.fsf@maximus.localdomain> (raw)
In-Reply-To: <58cb370e0803050846t7dbd65d6ocfec7ca5e93aa6db@mail.gmail.com> (Bartlomiej Zolnierkiewicz's message of "Wed\, 5 Mar 2008 17\:46\:08 +0100")
"Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com> writes:
> [ Actually, I'm not surprised as we are getting patches/reports for much
> older/buggier hardware... After all we are doing Linux not some other
> OS whose every release obsoletes the old hardware. ;-) ]
It isn't just about old/buggy hardware (personally I'm using much
older items). The DTLA disks had "rather" short MTBF, with something
like 30% returns in the first year after purchase, according to a
friendly distributor. Despite firmware upgrades, they were unfixable.
--
Krzysztof Halasa
next prev parent reply other threads:[~2008-03-05 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 23:16 [patch 3/3] pata: "I do not think it means, what you think it means." akpm
2008-03-05 1:34 ` Bartlomiej Zolnierkiewicz
2008-03-05 1:30 ` Andrew Morton
2008-03-05 1:54 ` Bartlomiej Zolnierkiewicz
2008-03-05 11:56 ` Alan Cox
2008-03-05 13:21 ` Bartlomiej Zolnierkiewicz
2008-03-05 14:39 ` Alan Cox
2008-03-05 16:13 ` Bartlomiej Zolnierkiewicz
2008-03-05 16:34 ` Krzysztof Halasa
2008-03-05 16:46 ` Bartlomiej Zolnierkiewicz
2008-03-05 16:55 ` Krzysztof Halasa [this message]
2008-03-05 17:22 ` Bartlomiej Zolnierkiewicz
2008-03-05 18:33 ` Zan Lynx
2008-03-06 1:33 ` Krzysztof Halasa
2008-03-06 11:13 ` Ville Syrjälä
2008-03-06 14:58 ` Mark Lord
2008-03-06 15:00 ` Mark Lord
2008-03-06 22:10 ` Krzysztof Halasa
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=m3ejap5cvz.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=bzolnier@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).