From: Johannes Weiner <hannes@saeurebad.de>
To: Stephen.Clark@seclark.us
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Jones <davej@codemonkey.org.uk>
Subject: Re: cpuinfo_cur_freq always max
Date: Tue, 18 Dec 2007 17:04:36 +0100 [thread overview]
Message-ID: <x71w9k6lbf.fsf@saeurebad.de> (raw)
In-Reply-To: <4767E500.9090802@seclark.us> (Stephen Clark's message of "Tue, 18 Dec 2007 10:19:28 -0500")
Hi,
Stephen Clark <Stephen.Clark@seclark.us> writes:
> userspace
Please supply the full dmesg output on the non-working kernel the
corresponding .config (or /proc/config.gz).
Added Dave to CC.
Hannes
next prev parent reply other threads:[~2007-12-18 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 17:51 cpuinfo_cur_freq always max Stephen Clark
2007-12-17 21:27 ` Johannes Weiner
[not found] ` <4766ECDB.1040203@seclark.us>
2007-12-17 22:09 ` Johannes Weiner
2007-12-18 15:19 ` Stephen Clark
2007-12-18 16:04 ` Johannes Weiner [this message]
2007-12-18 21:39 ` Stephen Clark
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=x71w9k6lbf.fsf@saeurebad.de \
--to=hannes@saeurebad.de \
--cc=Stephen.Clark@seclark.us \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@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