public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Padraig Brady <padraig.brady@corvil.com>
Cc: Dominik Brodowski <linux@brodo.de>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	cpufreq@www.linux.org.uk
Subject: Re: [PATCH][2.5.35] CPU frequency and voltage scaling (0/5)
Date: Tue, 17 Sep 2002 10:48:13 -0700	[thread overview]
Message-ID: <3D876ADD.9090800@transmeta.com> (raw)
In-Reply-To: 3D870734.9080301@corvil.com

Padraig Brady wrote:
> 
> This is much better, but I preferred Dave Jones' suggestion of
> supporting stackable policies as I can see no end to them:
> max_cpu_temp, temp_hysteresis, favor_fast_{fsb,multiplier}, ...
> 

It would be especially interesting if the policy name can be a loadable 
module (via kmod.)

	-hpa



      reply	other threads:[~2002-09-17 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-17  9:30 [PATCH][2.5.35] CPU frequency and voltage scaling (0/5) Dominik Brodowski
2002-09-17 10:43 ` Padraig Brady
2002-09-17 17:48   ` H. Peter Anvin [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=3D876ADD.9090800@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.de \
    --cc=padraig.brady@corvil.com \
    --cc=torvalds@transmeta.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