From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Zhang, Rui" <rui.zhang@intel.com>
Cc: Pavel Machek <pavel@suse.cz>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
trenn@suse.de
Subject: Re: [Patch v2] Implement thermal limiting in the generic thermal class
Date: Wed, 18 Jun 2008 10:56:46 +0100 [thread overview]
Message-ID: <20080618095646.GA20079@srcf.ucam.org> (raw)
In-Reply-To: <823A93EED437D048963A3697DB0E35DE0171191C@pdsmsx414.ccr.corp.intel.com>
On Wed, Jun 18, 2008 at 05:28:01PM +0800, Zhang, Rui wrote:
> One thing I'm concerning is that if we could enable polling in Linux.
> Bug #8842 shows that polling may break some laptops.
> And we have known that windows never enable polling.
> Although this patch will not break the laptop in #8842, it still may
> bring some potential risks if we enable polling in Linux.
> IMO, a dmi entry would be much more acceptable...
If it breaks anything, we can revisit the decision. I'd be surprised if
it did.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-06-18 9:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 10:06 [PATCH] Clean up thermal API Matthew Garrett
2008-06-11 16:42 ` [PATCH] More cleanup of the " Matthew Garrett
2008-06-11 16:58 ` [RFC] Implement thermal limiting in generic thermal class Matthew Garrett
2008-06-12 2:25 ` Zhang Rui
2008-06-12 9:28 ` Matthew Garrett
2008-06-12 1:29 ` [PATCH] More cleanup of the thermal API Zhang Rui
2008-06-12 1:26 ` [PATCH] Clean up " Zhang Rui
2008-06-16 8:55 ` [PATCH v2] " Matthew Garrett
2008-06-16 9:26 ` [Patch v2] Implement thermal limiting in the generic thermal class Matthew Garrett
2008-06-17 18:53 ` Pavel Machek
2008-06-18 9:28 ` Zhang, Rui
2008-06-18 9:56 ` Matthew Garrett [this message]
2008-06-17 15:54 ` [PATCH] Clean up thermal API Pavel Machek
2008-06-17 15:59 ` Pavel Machek
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=20080618095646.GA20079@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rui.zhang@intel.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