cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 71931] intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed
Date: Wed, 12 Mar 2014 20:52:48 +0000	[thread overview]
Message-ID: <bug-71931-12968-A6RERecWyT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71931-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=71931

--- Comment #3 from Patrik Lundquist <patrik.lundquist@gmail.com> ---
Patch tested on an Intel Xeon CPU E3-1240 V2 @ 3.40GHz (fam: 06, model: 3a,
stepping: 09) which is also an Ivy Bridge.

The intel_pstate driver loads fine and cpufreq_driver->get() is no longer
called when cpufreq adds the CPUs.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2014-03-12 20:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11 20:41 [Bug 71931] New: intel_pstate: cpufreq: __cpufreq_add_dev: ->get() failed bugzilla-daemon
2014-03-11 23:16 ` [Bug 71931] " bugzilla-daemon
2014-03-12 11:18 ` bugzilla-daemon
2014-03-12 11:19 ` bugzilla-daemon
2014-03-12 20:52 ` bugzilla-daemon [this message]
2014-03-17  3:18 ` 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=bug-71931-12968-A6RERecWyT@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).