From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 14084] cpufreq ondemand always 100% on one of the intel cores
Date: Wed, 18 Jan 2012 01:52:33 GMT [thread overview]
Message-ID: <201201180152.q0I1qXbR018252@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-14084-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=14084
Zhang Rui <rui.zhang@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |rui.zhang@intel.com
--- Comment #4 from Zhang Rui <rui.zhang@intel.com> 2012-01-18 01:52:33 ---
It's great that kernel bugzilla is back.
can you please verify if the problem still exists in the latest upstream
kernel?
--
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:[~2012-01-18 1:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14084-12968@https.bugzilla.kernel.org/>
2012-01-18 1:52 ` bugzilla-daemon [this message]
2012-05-13 14:38 ` [Bug 14084] cpufreq ondemand always 100% on one of the intel cores 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=201201180152.q0I1qXbR018252@bugzilla.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