From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 72211] intel_pstate Haswell CPU is not entering hardware package idle state
Date: Fri, 18 Apr 2014 02:27:03 +0000 [thread overview]
Message-ID: <bug-72211-12968-4yVIKAdhPN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-72211-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=72211
Lan Tianyu <tianyu.lan@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tianyu.lan@intel.com
Component|cpufreq |Network
Assignee|cpufreq@vger.kernel.org |drivers_network@kernel-bugs
| |.osdl.org
Product|Power Management |Drivers
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2014-04-18 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 16:30 [Bug 72211] New: intel_pstate Haswell CPU is not entering hardware package idle state bugzilla-daemon
2014-03-20 12:22 ` [Bug 72211] " bugzilla-daemon
2014-03-24 21:14 ` bugzilla-daemon
2014-04-18 2:27 ` bugzilla-daemon [this message]
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=bug-72211-12968-4yVIKAdhPN@https.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).