summaryrefslogtreecommitdiffstats
path: root/lib/locking-selftest-hardirq.h
diff options
context:
space:
mode:
authorRoland Dreier <rdreier@cisco.com>2009-09-30 22:58:03 +0200
committerLen Brown <len.brown@intel.com>2009-10-03 07:06:12 +0200
commit53412c5b1225db77f7ac04b6a5351e60ea2a280f (patch)
tree6d4399d7ab5c7fda6f8acc5d9e68f22dc3b6a198 /lib/locking-selftest-hardirq.h
parentACPI: Fix bound checks for copy_from_user in the acpi /proc code (diff)
downloadlinux-53412c5b1225db77f7ac04b6a5351e60ea2a280f.tar.xz
linux-53412c5b1225db77f7ac04b6a5351e60ea2a280f.zip
ACPI: kill overly verbose "throttling states" log messages
I was recently lucky enough to get a 64-CPU system. The processors actually have T-states, so my kernel log ends up with 64 lines like: ACPI: Processor [CPU0] (supports xx throttling states) This is pretty useless clutter because - this info is already available after boot from /proc/acpi/processor/CPUnn/throttling - there's also an ACPI_DEBUG_PRINT() in processor_throttling.c that gives the same info on boot for anyone who *really* cares. So just delete the code that prints the throttling states in processor_core.c. Signed-off-by: Roland Dreier <rolandd@cisco.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'lib/locking-selftest-hardirq.h')
0 files changed, 0 insertions, 0 deletions