From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 49231] Single CPU bound process results in non-optimal turbo boost configuration
Date: Mon, 28 Jan 2013 23:57:39 +0000 (UTC) [thread overview]
Message-ID: <20130128235739.20C7111FF1B@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-49231-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=49231
Len Brown <lenb@kernel.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
prev parent reply other threads:[~2013-01-28 23:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 23:56 [Bug 49231] New: Single CPU bound process results in non-optimal turbo boost configuration bugzilla-daemon
2012-10-22 13:44 ` [Bug 49231] " bugzilla-daemon
2012-10-22 13:57 ` bugzilla-daemon
2012-10-22 23:02 ` bugzilla-daemon
2012-10-23 2:09 ` bugzilla-daemon
2012-10-23 10:20 ` bugzilla-daemon
2012-10-24 4:21 ` bugzilla-daemon
2012-10-24 11:44 ` bugzilla-daemon
2013-01-28 23:57 ` bugzilla-daemon
2013-01-28 23:57 ` 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=20130128235739.20C7111FF1B@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).