linux-kernel - Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060731162046.GA4631@redhat.com>
Date:	Mon, 31 Jul 2006 12:20:46 -0400
From:	Dave Jones <davej@...hat.com>
To:	bert hubert <bert.hubert@...herlabs.nl>,
	Alexey Starikovskiy <alexey_y_starikovskiy@...ux.intel.com>,
	linux-kernel@...r.kernel.org, zwane@....linux.org.uk,
	venkatesh.pallipadi@...el.com, tony@...mide.com, akpm@...l.org,
	cpufreq@...ts.linux.org.uk, len.brown@...el.com
Subject: Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on	pentium4

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/