From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: davej@codemonkey.org.uk, Christian Krafft <krafft@de.ibm.com>,
cpufreq@lists.linux.org.uk
Subject: Re: cpufreq_set_policy removed
Date: Thu, 07 Jun 2007 09:01:18 +1000 [thread overview]
Message-ID: <1181170878.31677.272.camel@localhost.localdomain> (raw)
In-Reply-To: <20070606214243.GX15955@bakeyournoodle.com>
On Thu, 2007-06-07 at 07:42 +1000, Tony Breeds wrote:
> Hi All,
> The git commit 632786ce9ff6206951ee4c84fe5c0d5c1d12f4cc reomved
> the "deprecated and buggy" cpufreq_set_policy(). In the linux powerpc
> tree we have a driver that's using it.
Ugh... we still use it ? I though we had fixed that ...
CC'ing Christian who maintains the CBE cpufreq driver.
Ben.
next prev parent reply other threads:[~2007-06-06 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 21:42 cpufreq_set_policy removed Tony Breeds
2007-06-06 23:01 ` Benjamin Herrenschmidt [this message]
2007-06-06 23:13 ` Dave Jones
2007-06-07 1:03 ` Tony Breeds
2007-06-15 17:45 ` Klaus.K Pedersen (Nokia-M/Helsinki)
2007-06-19 12:14 ` Thomas Renninger
2007-06-20 21:20 ` Myron Stowe
2007-06-23 17:32 ` Thomas Renninger
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=1181170878.31677.272.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=krafft@de.ibm.com \
--cc=tony@bakeyournoodle.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