From: "Anthony L. Awtrey" <tony@awtrey.com>
To: trenn@suse.de
Cc: Dave Jones <davej@codemonkey.org.uk>, cpufreq@lists.linux.org.uk
Subject: Re: acpi_cpufreq stepping issue on Pentium M 1.2GHz
Date: Wed, 21 May 2008 08:51:04 -0400 [thread overview]
Message-ID: <48341AB8.3090401@awtrey.com> (raw)
In-Reply-To: <1211279939.21269.403.camel@queen.suse.de>
On 05/20/2008 06:38 AM, Thomas Renninger wrote:
> It could be that you hit a bug that might get fixed with a recent
> commit:
> commit e56a727b023d40d1adf660168883f30f2e6abe0a
> Author: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> Date: Mon Apr 28 15:13:43 2008 -0400
>
> [CPUFREQ] Make acpi-cpufreq more robust against BIOS freq changes
> behind our back.
Hi,
Sorry for the public display of ignorance, but I can't seem to find this
patch as a simple diff so I can test it in one of my vanilla kernel
builds (either 2.6.24.2 or 2.6.25.4, please). Can you provide me a
general patch or some example git commands to get a build-able source tree?
Tony
next prev parent reply other threads:[~2008-05-21 12:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 18:15 acpi_cpufreq stepping issue on Pentium M 1.2GHz Anthony L. Awtrey
2008-05-19 0:08 ` Dave Jones
2008-05-19 11:29 ` Anthony L. Awtrey
2008-05-19 13:14 ` Dave Jones
2008-05-19 13:38 ` Anthony L. Awtrey
2008-05-20 10:38 ` Thomas Renninger
2008-05-21 12:51 ` Anthony L. Awtrey [this message]
2008-05-21 13:08 ` [PATCH] Make acpi-cpufreq more robust against BIOS freq changes behind our back Thomas Renninger
2008-05-21 13:15 ` Thomas Renninger
2008-05-21 15:00 ` [stable] " Greg KH
2008-05-21 18:48 ` Anthony L. Awtrey
2008-05-23 9:20 ` Thomas Renninger
2008-05-21 15:46 ` Anthony L. Awtrey
2008-06-02 22:36 ` [stable] " Chris Wright
2008-06-11 14:33 ` Thomas Renninger
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=48341AB8.3090401@awtrey.com \
--to=tony@awtrey.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=trenn@suse.de \
/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).