From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Len Brown <lenb@kernel.org>, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2/2] Add a passive cooling trip point if the firmware doesn't define one
Date: Thu, 15 May 2008 13:02:34 +0100 [thread overview]
Message-ID: <20080515120234.GA23538@srcf.ucam.org> (raw)
In-Reply-To: <87iqxfzt4f.fsf@basil.nowhere.org>
On Thu, May 15, 2008 at 01:47:28PM +0200, Andi Kleen wrote:
> Wouldn't it be possible to add a D610 specific quirk that
> simply adds a trip point for that machine only?
>
> As long as the problem is not wide-spread over many models
> a quirk is a reasonable solution.
There are plenty of other machines that have this issue, but there
doesn't seem to be any especially good pattern to them. In marginal
cases it may even depend on the manufacturing batch.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-05-15 12:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 1:00 [PATCH] Fix polling policy in the absence of _TZP Matthew Garrett
2008-05-14 1:03 ` [PATCH 1/2] Add a list of processor objects to the ACPI core Matthew Garrett
2008-05-14 1:08 ` [PATCH 2/2] Add a passive cooling trip point if the firmware doesn't define one Matthew Garrett
2008-05-14 3:30 ` Len Brown
2008-05-14 9:33 ` Matthew Garrett
2008-05-14 15:37 ` Len Brown
2008-05-14 23:01 ` Matthew Garrett
2008-05-15 0:55 ` Zhang Rui
2008-05-15 1:04 ` Matthew Garrett
[not found] ` <1210814699.2929.10.camel@rzhang-crestline.sh.intel.com>
[not found] ` <20080515015831.GA14829@srcf.ucam.org>
2008-05-15 2:15 ` Zhang Rui
2008-05-15 2:24 ` Matthew Garrett
2008-05-15 3:06 ` Zhang Rui
2008-05-15 11:40 ` Matthew Garrett
2008-05-15 11:47 ` Andi Kleen
2008-05-15 12:02 ` Matthew Garrett [this message]
2008-05-14 3:19 ` [PATCH] Fix polling policy in the absence of _TZP Len Brown
2008-05-14 10:14 ` Matthew Garrett
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=20080515120234.GA23538@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=andi@firstfloor.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@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.