From: Eduardo Valentin <edubezval@gmail.com>
To: "Zhang, Rui" <rui.zhang@intel.com>
Cc: Jean Delvare <jdelvare@suse.de>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: Thermal governors non-modularity
Date: Mon, 22 Feb 2016 10:56:57 -0800 [thread overview]
Message-ID: <20160222185655.GA18736@localhost.localdomain> (raw)
In-Reply-To: <744357E9AAD1214791ACBA4B0B9092633A963443@SHSMSX101.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
Hello
On Mon, Feb 22, 2016 at 07:06:17AM +0000, Zhang, Rui wrote:
> I tried to use them as module in the first place, but failed for some reason. I cannot recall the root cause, but I will try to check this and reply to you later. :)
>
Yeah, there was bug in the boot sequencing that would leave fans on all
the time. Then you decided to make everything builtin:
http://marc.info/?l=linux-kernel&m=136085598604095&w=2
> Thanks,
> rui
>
> > -----Original Message-----
> > From: Jean Delvare [mailto:jdelvare@suse.de]
> > Sent: Saturday, February 20, 2016 9:05 PM
> > To: linux-pm@vger.kernel.org
> > Cc: Zhang, Rui <rui.zhang@intel.com>; Eduardo Valentin
> > <edubezval@gmail.com>
> > Subject: Thermal governors non-modularity
> > Importance: High
> >
> > Hi Rui, Eduardo,
> >
> > Is there any fundamental reason why thermal governors can't be built as
> > modules? We have more and more of them, 5 now, and the most recent is
> > fairly big... Would be much more practical if they could be built as modules
> > and loaded at run-time only as needed.
I agree here. We just to make sure we don't regress here.
BR,
> >
> > Thanks,
> > --
> > Jean Delvare
> > SUSE L3 Support
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-02-22 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 13:04 Thermal governors non-modularity Jean Delvare
2016-02-22 7:06 ` Zhang, Rui
2016-02-22 18:56 ` Eduardo Valentin [this message]
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=20160222185655.GA18736@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=jdelvare@suse.de \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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).