From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 177161] CPU frequencies in /proc/cpuinfo aren't dynamically updated
Date: Tue, 11 Oct 2016 00:02:22 +0000 [thread overview]
Message-ID: <bug-177161-137361-2EpRBF8nbw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-177161-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=177161
Len Brown <lenb@kernel.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lenb@kernel.org
Assignee|linux-pm@vger.kernel.org |lenb@kernel.org
--- Comment #3 from Len Brown <lenb@kernel.org> ---
I proposed a patch to make /proc/cpuinfo accurate several months ago.
Red Hat didn't like it, arguing that changing values is a support issue.
So there was not agreement on what to do here -- let's go find out if
it changed by mistake...
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2016-10-11 0:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 13:15 [Bug 177161] New: CPU frequencies in /proc/cpuinfo aren't dynamically updated bugzilla-daemon
2016-10-10 13:15 ` [Bug 177161] " bugzilla-daemon
2016-10-10 13:17 ` bugzilla-daemon
2016-10-11 0:02 ` 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-177161-137361-2EpRBF8nbw@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-pm@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).