* PATCH: 2.6.10 - Fix microcode text
@ 2004-12-26 23:44 Alan Cox
0 siblings, 0 replies; only message in thread
From: Alan Cox @ 2004-12-26 23:44 UTC (permalink / raw)
To: torvalds, Linux Kernel Mailing List
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;
}
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-12-27 0:50 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-12-26 23:44 PATCH: 2.6.10 - Fix microcode text Alan Cox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®