linux/arch/i386/kernel/cpu
Zachary Amsden 18420001d6 [PATCH] i386: Clean up arch/i386/kernel/cpu/mcheck/p4.c
No, just no.  You do not use goto to skip a code block.  You do not
return an obvious variable from a singly-inlined function and give
the function a return value.  You don't put unexplained comments
about kmalloc in code which doesn't do dynamic allocation.  And
you don't leave stray warnings around for no good reason.

Also, when possible, it is better to use block scoped variables
because gcc can sometime generate better code.

Signed-off-by: Zachary Amsden <zach@vmware.com>
Signed-off-by: Andi Kleen <ak@suse.de>
2007-05-02 19:27:16 +02:00
..
cpufreq Longhaul - Revert ACPI C3 on Longhaul ver. 2 2007-04-20 22:56:29 -07:00
mcheck [PATCH] i386: Clean up arch/i386/kernel/cpu/mcheck/p4.c 2007-05-02 19:27:16 +02:00
mtrr [PATCH] i386: mtrr range check correction 2007-05-02 19:27:05 +02:00
amd.c [PATCH] x86: Don't use MWAIT on AMD Family 10 2007-05-02 19:27:12 +02:00
bugs.c [PATCH] i386: Clean up asm-i386/bugs.h 2007-05-02 19:27:12 +02:00
centaur.c
common.c [PATCH] i386: Fix UP gdt bugs 2007-05-02 19:27:16 +02:00
cpu.h
cyrix.c [PATCH] x86: Log reason why TSC was marked unstable 2007-05-02 19:27:08 +02:00
intel.c
intel_cacheinfo.c
Makefile [PATCH] i386: Clean up asm-i386/bugs.h 2007-05-02 19:27:12 +02:00
nexgen.c
proc.c [PATCH] x86: remove constant_tsc reporting from /proc/cpuinfo' power flags 2007-05-02 19:27:09 +02:00
rise.c
transmeta.c [PATCH] i386: Fix warning in cpu initialization 2007-02-13 13:26:25 +01:00
umc.c