From: Ingo Molnar <mingo@elte.hu>
To: Hans Schou <linux@schou.dk>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH] More informative about unknown CPU
Date: Fri, 10 Oct 2008 17:04:58 +0200 [thread overview]
Message-ID: <20081010150458.GG11695@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0810092014190.7473@sko.w0.dk>
* Hans Schou <linux@schou.dk> wrote:
> Hi
>
> Write the name of the unknown vendor_id to output instead of just
> "file not found".
>
> Tag changed to 'vendor_id' as used in /proc/cpuinfo
>
> Signed-off-by: Hans Schou <linux@schou.dk>
applied to tip/x86/unify-cpu-detect, thanks Hans!
> --- linux.trees.git/arch/x86/kernel/cpu/common.c.orig 2008-10-09 17:33:29.000000000 +0200
> +++ linux.trees.git/arch/x86/kernel/cpu/common.c 2008-10-09 17:33:59.000000000 +0200
> @@ -413,7 +413,7 @@ static void __cpuinit get_cpu_vendor(str
>
> if (!printed) {
> printed++;
> - printk(KERN_ERR "CPU: Vendor unknown, using generic init.\n");
> + printk(KERN_ERR "CPU: vendor_id '%s' unknown, using generic init.\n", v);
> printk(KERN_ERR "CPU: Your system may be unstable.\n");
btw., this was whitespace damaged (i fixed that up by hand). See
Documentation/email-clients.txt about how to set up the email client.
(or, when you send x86 patches, you can attach the patch as a MIME
attachment)
Ingo
next prev parent reply other threads:[~2008-10-10 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 18:47 [PATCH] More informative about unknown CPU Hans Schou
2008-10-10 15:04 ` Ingo Molnar [this message]
2008-10-10 16:20 ` Yinghai Lu
2008-10-10 16:24 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081010150458.GG11695@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@schou.dk \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox