From: Dave Jones <davej@redhat.com>
To: bert hubert <bert.hubert@netherlabs.nl>,
Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>,
linux-kernel@vger.kernel.org, zwane@arm.linux.org.uk,
venkatesh.pallipadi@intel.com, tony@atomide.com, akpm@osdl.org,
cpufreq@lists.linux.org.uk, len.brown@intel.com
Subject: Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
Date: Mon, 31 Jul 2006 12:20:46 -0400 [thread overview]
Message-ID: <20060731162046.GA4631@redhat.com> (raw)
In-Reply-To: <20060731070800.GA22205@outpost.ds9a.nl>
On Mon, Jul 31, 2006 at 09:08:01AM +0200, bert hubert wrote:
> > went ok. I wonder if something changed in acpi recently that caused this
> > change in behaviour ? Len ?
>
> Dave,
>
> I'm no expert but I think it was you that made this change in
> http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blobdiff;h=567b39bea07e4fbbe091b265b010905e3d30ff5a;hp=1a7bdcef19261deff5a7ea8ee13d5a8ddb434a19;hb=911cb74bb9e77e40749abc2fca6fe74d87d940f3;f=arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
>
> + /* Do initialization in ACPI core */
> + acpi_processor_preregister_performance(acpi_perf_data);
> + return 0;
> +}
>
> :-)
I'm puzzled. As that commit message doesn't match the diff.
If you click "commitdiff", you'll see the actual commit for that msg,
which is a one-liner.
Your change in your previous mail makes sense to me though,
so I'll commit it to cpufreq.git later today.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-07-31 16:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 12:08 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4 bert hubert
2006-07-30 16:07 ` Tomasz Torcz
2006-07-30 16:51 ` 2.6.17 -> " bert hubert
2006-07-30 18:07 ` Alexey Starikovskiy
2006-07-30 18:44 ` bert hubert
2006-07-30 19:01 ` Dave Jones
2006-07-30 19:19 ` bert hubert
2006-07-31 7:08 ` bert hubert
2006-07-31 16:20 ` Dave Jones [this message]
2006-07-31 18:57 ` bert hubert
2006-07-31 20:38 ` Dave Jones
2006-07-30 17:45 ` Zwane Mwaikambo
2006-07-31 5:56 ` Tomasz Torcz
2006-07-31 14:04 ` Zwane Mwaikambo
2006-07-31 15:22 ` Tomasz Torcz
2006-07-30 19:46 ` Arjan van de Ven
2006-07-30 19:53 ` bert hubert
2006-07-31 7:50 ` David Rees
2006-07-31 8:12 ` bert hubert
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=20060731162046.GA4631@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=alexey_y_starikovskiy@linux.intel.com \
--cc=bert.hubert@netherlabs.nl \
--cc=cpufreq@lists.linux.org.uk \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=zwane@arm.linux.org.uk \
/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