From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 13035] select for cpufreq/ files
Date: Tue, 1 Feb 2011 01:23:11 GMT [thread overview]
Message-ID: <201102010123.p111NB3Z016674@demeter1.kernel.org> (raw)
In-Reply-To: <bug-13035-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=13035
ykzhao <yakui.zhao@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yakui.zhao@intel.com
--- Comment #1 from ykzhao <yakui.zhao@intel.com> 2011-02-01 01:23:09 ---
Hi,
Why do you expect to use the "select" function for the
scaling_availabe_frequencies interface? What do you want to monitor? It can
immediately return the available frequencies supported by the corresponding
CPU. At most cases the available frequencies can't be changed.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next parent reply other threads:[~2011-02-01 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13035-12968@https.bugzilla.kernel.org/>
2011-02-01 1:23 ` bugzilla-daemon [this message]
2011-02-01 2:47 ` [Bug 13035] select for cpufreq/ files bugzilla-daemon
2011-07-30 5:56 ` bugzilla-daemon
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=201102010123.p111NB3Z016674@demeter1.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@vger.kernel.org \
/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