From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 60211] intel_pstate driver missing ids for some supported CPUs
Date: Fri, 28 Jun 2013 04:09:18 +0000 (UTC) [thread overview]
Message-ID: <20130628040918.B971E11F978@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-60211-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60211
Viresh Kumar <viresh.kumar@linaro.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |viresh.kumar@linaro.org
--- Comment #1 from Viresh Kumar <viresh.kumar@linaro.org> 2013-06-28 04:09:17 ---
Hi Nell,
If this is already solved why not send a patch to dirk and list. And we can get
it in quickly. Maybe for 3.11, before Rafael sends a pull request. :)
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2013-06-28 4:09 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 ` bugzilla-daemon [this message]
2013-07-01 2:23 ` [Bug 60211] " bugzilla-daemon
2013-12-09 8:25 ` 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=20130628040918.B971E11F978@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.