From: Myron Stowe <myron.stowe@hp.com>
To: trenn@suse.de, Dave Jones <davej@redhat.com>
Cc: cpufreq <cpufreq@lists.linux.org.uk>
Subject: Re: cpufreq_set_policy removed
Date: Wed, 20 Jun 2007 15:20:31 -0600 [thread overview]
Message-ID: <1182374431.8149.30.camel@localhost> (raw)
In-Reply-To: <1182255270.28514.620.camel@queen.suse.de>
Thomas, Dave:
Do either of you have a problem with the existence of
cpufreq_set_policy() or was it only removed because there were no
remaining callers in the tree and it had bugs?
The reason why I ask is that I have been working on a module that
changes cpufreq governors and I don't see any other way for a module to
be able to change governors without this interface.
If there is another way please let me know. Otherwise I would like to
fix the cpufreq_set_policy() related bugs and make it available for
modules to use.
Myron
--
Myron Stowe HP Open Source & Linux Org
next prev parent reply other threads:[~2007-06-20 21:20 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
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 [this message]
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=1182374431.8149.30.camel@localhost \
--to=myron.stowe@hp.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.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