From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 60211] intel_pstate driver missing ids for some supported CPUs
Date: Mon, 09 Dec 2013 08:25:08 +0000 [thread overview]
Message-ID: <bug-60211-12968-rEXicDnyKS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60211-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60211
Aaron Lu <aaron.lu@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #3 from Aaron Lu <aaron.lu@intel.com> ---
commit 6cdcdb793791f776ea9408581b1242b636d43b37
Author: Nell Hardcastle <nell@spicious.com>
Date: Sun Jun 30 15:58:57 2013 -0700
intel_pstate: Add Haswell CPU models
upstreamed.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2013-12-09 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 1:13 [Bug 60211] New: intel_pstate driver missing ids for some supported CPUs bugzilla-daemon
2013-06-28 4:09 ` [Bug 60211] " bugzilla-daemon
2013-07-01 2:23 ` bugzilla-daemon
2013-12-09 8:25 ` 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-60211-12968-rEXicDnyKS@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 NNTP newsgroup(s).