From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jack Howarth <howarth@bromo.msbb.uc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: W2100Z Critical temperature explained
Date: Tue, 25 Oct 2005 19:42:01 +0100 [thread overview]
Message-ID: <1130265721.25191.58.camel@localhost.localdomain> (raw)
In-Reply-To: <20051025164339.431C81DC06D@bromo.msbb.uc.edu>
On Maw, 2005-10-25 at 12:43 -0400, Jack Howarth wrote:
> various Linux kernels. Certainly in cases like these where destruction
> can occur due to the bugs in the firmware, this merits being passed
> along to the Linux kernel users.
If that is indeed the case and as serious as you describe then I'm sure
Sun will be contacting all their customers urgently to advise them of
the flawed hardware as they would with faulty PSU's or other items.
Trying to track each of the billion broken PCs in the world work on a
given day with a given card combination is something thats almost
computationally infeasible
Alan
next prev parent reply other threads:[~2005-10-25 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 16:43 W2100Z Critical temperature explained Jack Howarth
2005-10-25 18:42 ` Alan Cox [this message]
2005-11-10 16:27 ` Kjartan Maraas
-- strict thread matches above, loose matches on Subject: below --
2005-10-25 23:02 Jack Howarth
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=1130265721.25191.58.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=howarth@bromo.msbb.uc.edu \
--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