From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Dominik Brodowski <linux@dominikbrodowski.net>,
Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>,
nagananda.chumbalkar@hp.com, linux-kernel@vger.kernel.org,
cpufreq@vger.kernel.org
Subject: Re: pcc-cpufreq bug [Was: Bug in cpufreq-utils (/sys/devices/system/cpu/cpu*/cpufreq/affected_cpus)?]
Date: Tue, 12 Apr 2011 21:48:11 +0100 [thread overview]
Message-ID: <20110412204811.GA9465@srcf.ucam.org> (raw)
In-Reply-To: <20110412203915.GB12827@comet.dominikbrodowski.net>
On Tue, Apr 12, 2011 at 10:39:15PM +0200, Dominik Brodowski wrote:
> To the pcc-cpufreq.c driver developers & maintainers: Is there _any_ way to
> properly set
>
> (struct cpufreq_policy *) -> cpus
> -> related_cpus
>
> in this driver?
The spec says we should be able to do this with the _PSD data. I'll look
into it.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-04-12 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 14:53 Bug in cpufreq-utils (/sys/devices/system/cpu/cpu*/cpufreq/affected_cpus)? Ulrich Windl
2011-04-12 20:39 ` pcc-cpufreq bug [Was: Bug in cpufreq-utils (/sys/devices/system/cpu/cpu*/cpufreq/affected_cpus)?] Dominik Brodowski
2011-04-12 20:48 ` Matthew Garrett [this message]
2011-04-13 10:55 ` Dominik Brodowski
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=20110412204811.GA9465@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=Ulrich.Windl@rz.uni-regensburg.de \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=nagananda.chumbalkar@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.