diff options
| author | Alan Cox <alan@lxorguk.ukuu.org.uk> | 2004-12-26 06:20:19 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2004-12-26 06:20:19 -0800 |
| commit | b09de82f7e76ea22a01c0de78d9fdc6861c34e00 (patch) | |
| tree | 2159cc5bed54d7fb012cf1a09d5fc0dc39643cd9 | |
| parent | 8123759620edf3dd0d8255ba3b4577f7c0685f33 (diff) | |
[PATCH] make microcode text less confusing
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>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
| -rw-r--r-- | arch/i386/kernel/microcode.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/i386/kernel/microcode.c b/arch/i386/kernel/microcode.c index 4de7538043f5..9fe9b42e8c29 100644 --- a/arch/i386/kernel/microcode.c +++ b/arch/i386/kernel/microcode.c @@ -364,7 +364,7 @@ static void do_update_one (void * unused) 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; } |