Messages in this thread Patch in this message | | | Subject | PATCH: 2.6.10 - Fix microcode text | From | Alan Cox <> | Date | Sun, 26 Dec 2004 23:44:00 +0000 |
| |
Red Hat got some confused customers due to this message. The confused user case is when they update the BIOS and all of a sudden we have "no suitable data" yet we did before. We (Arjan van de Ven) thus changed it to "No new microcode" which is much much clearer.
Signed-off-by: Alan Cox <alan@redhat.com>
diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.10/arch/i386/kernel/microcode.c linux-2.6.10/arch/i386/kernel/microcode.c --- linux.vanilla-2.6.10/arch/i386/kernel/microcode.c 2004-12-25 21:15:32.000000000 +0000 +++ linux-2.6.10/arch/i386/kernel/microcode.c 2004-12-26 17:30:43.000000000 +0000 @@ -364,7 +364,7 @@ struct ucode_cpu_info *uci = ucode_cpu_info + cpu_num; if (uci->mc == NULL) { - printk(KERN_INFO "microcode: No suitable data for CPU%d\n", cpu_num); + printk(KERN_INFO "microcode: No new microcode data for CPU%d\n", cpu_num); return; } - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |