From: Len Brown <lenb@kernel.org>
To: Thomas Renninger <trenn@suse.de>
Cc: "Moore, Robert" <robert.moore@intel.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
devel@acpica.org, stuart_hayes@dell.com
Subject: Re: [PATCH] ACPICA: Do not hang at mutex forever if BIOS tries to release global lock
Date: Fri, 15 Oct 2010 22:25:23 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1010152222150.2971@localhost.localdomain> (raw)
In-Reply-To: <201010081240.15203.trenn@suse.de>
> There seem to be chipsets which can get this wrong (especially after a kexec
> boot on Linux).
<recording>
As kexec is fundamentally unreliable by design,
why should reliable software be modified for its beneift?
</recording>
-Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-10-16 2:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 10:40 [PATCH] ACPICA: Do not hang at mutex forever if BIOS tries to release global lock Thomas Renninger
2010-10-08 14:54 ` Moore, Robert
2010-10-16 2:25 ` Len Brown [this message]
2010-10-18 15:37 ` Stuart_Hayes
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=alpine.LFD.2.00.1010152222150.2971@localhost.localdomain \
--to=lenb@kernel.org \
--cc=devel@acpica.org \
--cc=linux-acpi@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=stuart_hayes@dell.com \
--cc=trenn@suse.de \
/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