The patch titled acpi: kill overly verbose "throttling states" log messages has been removed from the -mm tree. Its filename was acpi-kill-overly-verbose-throttling-states-log-messages.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: acpi: kill overly verbose "throttling states" log messages From: Roland Dreier <rdreier@xxxxxxxxx> 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@xxxxxxxxx> Cc: Len Brown <lenb@xxxxxxxxxx> Cc: Bjorn Helgaas <bjorn.helgaas@xxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/acpi/processor_core.c | 7 ------- 1 file changed, 7 deletions(-) diff -puN drivers/acpi/processor_core.c~acpi-kill-overly-verbose-throttling-states-log-messages drivers/acpi/processor_core.c --- a/drivers/acpi/processor_core.c~acpi-kill-overly-verbose-throttling-states-log-messages +++ a/drivers/acpi/processor_core.c @@ -863,13 +863,6 @@ static int acpi_processor_add(struct acp goto err_remove_sysfs; } - if (pr->flags.throttling) { - printk(KERN_INFO PREFIX "%s [%s] (supports", - acpi_device_name(device), acpi_device_bid(device)); - printk(" %d throttling states", pr->throttling.state_count); - printk(")\n"); - } - return 0; err_remove_sysfs: _ Patches currently in -mm which might be from rdreier@xxxxxxxxx are linux-next.patch ecryptfs-another-lockdep-issue.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