The patch titled
acpi_processor_ppc_notifier(): correct bound checking from the value returned from _PPC method
has been removed from the -mm tree. Its filename was
correct-bound-checking-from-the-value-returned-from-_ppc-method.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: acpi_processor_ppc_notifier(): correct bound checking from the value returned from _PPC method
From: Dave Jones <davej@xxxxxxxxxx>
processor_perflib.c::acpi_processor_ppc_notifier() check if the value
returned by the processor's _PPC method is 0 and return failed if so. This
is wrong since 0 indicate that the bios think the processor can go to the
highest frequency. This patch for example fix the HP NX 6125 to allow its
highest frequency to be available.
Signed-off-by: Bruno Ducrot <ducrot@xxxxxxxxxxxx>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@xxxxxxxxx>
Signed-off-by: Dave Jones <davej@xxxxxxxxxx>
Cc: Len Brown <lenb@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
drivers/acpi/processor_perflib.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff -puN drivers/acpi/processor_perflib.c~correct-bound-checking-from-the-value-returned-from-_ppc-method drivers/acpi/processor_perflib.c
--- a/drivers/acpi/processor_perflib.c~correct-bound-checking-from-the-value-returned-from-_ppc-method
+++ a/drivers/acpi/processor_perflib.c
@@ -83,10 +83,8 @@ static int acpi_processor_ppc_notifier(s
goto out;
ppc = (unsigned int)pr->performance_platform_limit;
- if (!ppc)
- goto out;
- if (ppc > pr->performance->state_count)
+ if (ppc >= pr->performance->state_count)
goto out;
cpufreq_verify_within_limits(policy, 0,
_
Patches currently in -mm which might be from davej@xxxxxxxxxx are
origin.patch
git-agpgart.patch
git-cpufreq.patch
remove-hotplug-cpu-crap-from-cpufreq.patch
swsusp-support-i386-systems-with-pae-or-without-pse.patch
more-list-debugging-context.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
