All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 33202] cpufreq-info-008 only reports maximum "current frequency", contradicts cpufreq stats and /proc/cpuinfo
Date: Wed, 13 Apr 2011 07:02:26 GMT	[thread overview]
Message-ID: <201104130702.p3D72Q33018668@demeter2.kernel.org> (raw)
In-Reply-To: <bug-33202-12968@https.bugzilla.kernel.org/>

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


LK <leho@kraav.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|cpufreq-info-008 only       |cpufreq-info-008 only
                   |reports maximum "current    |reports maximum "current
                   |frequency", contradict      |frequency", contradicts
                   |cpufreq stats and           |cpufreq stats and
                   |/proc/cpuinfo               |/proc/cpuinfo




-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  reply	other threads:[~2011-04-13  7:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13  7:02 [Bug 33202] New: cpufreq-info-008 only reports maximum "current frequency", contradict cpufreq stats and /proc/cpuinfo bugzilla-daemon
2011-04-13  7:02 ` bugzilla-daemon [this message]
2011-04-13  7:02 ` [Bug 33202] cpufreq-info 008 only reports maximum "current frequency", contradicts " bugzilla-daemon
2011-04-13 10:54 ` bugzilla-daemon
2011-04-13 12:57 ` bugzilla-daemon
2011-04-14 15:18 ` bugzilla-daemon
2012-01-18  3:27 ` bugzilla-daemon
2012-01-18  3:27 ` 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=201104130702.p3D72Q33018668@demeter2.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.