From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 211791] AMD CPU /proc/cpuinfo reported max potential boost frequency instead of actual operating frequency
Date: Fri, 06 May 2022 19:10:44 +0000 [thread overview]
Message-ID: <bug-211791-137361-yQIyz9AyQK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211791-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211791
Mario Limonciello (AMD) (mario.limonciello@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |CODE_FIX
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2022-05-06 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 1:41 [Bug 211791] New: AMD CPU /proc/cpuinfo reported max potential boost frequency instead of actual operating frequency bugzilla-daemon
2021-02-16 1:41 ` [Bug 211791] " bugzilla-daemon
2021-03-13 10:41 ` bugzilla-daemon
2021-04-20 8:55 ` bugzilla-daemon
2021-04-20 10:20 ` Huang Rui
2021-04-20 10:20 ` bugzilla-daemon
2021-04-30 18:22 ` bugzilla-daemon
2021-05-14 2:27 ` bugzilla-daemon
2022-05-06 19:10 ` 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-211791-137361-yQIyz9AyQK@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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).