From: Ingo Molnar <mingo@elte.hu>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [trivial] fix missing space in printk
Date: Fri, 5 Dec 2008 13:10:46 +0100 [thread overview]
Message-ID: <20081205121046.GA28662@elte.hu> (raw)
In-Reply-To: <4939139C.8090806@msgid.tls.msk.ru>
* Michael Tokarev <mjt@tls.msk.ru> wrote:
> Just come across this when booting on an old hw.. Looks somewhat ugly,
> that single missing space ;)
>
> And oh,
>
> Signed-Off-By: Michael Tokarev <mjt@tls.msk.ru>
>
> ;)
applied to tip/x86/cleanups.
> --- a/arch/x86/kernel/smpboot.c 2008-10-10 02:13:53.000000000 +0400
> +++ b/arch/x86/kernel/smpboot.c 2008-12-05 14:39:29.608353301 +0300
> @@ -1084,7 +1084,7 @@ static int __init smp_sanity_check(unsig
> #endif
>
> if (!physid_isset(hard_smp_processor_id(), phys_cpu_present_map)) {
> - printk(KERN_WARNING "weird, boot CPU (#%d) not listed"
> + printk(KERN_WARNING "weird, boot CPU (#%d) not listed "
> "by the BIOS.\n", hard_smp_processor_id());
btw., the reason for that bug was the incorrect line break in the middle
of a string - we humans just dont notice a missing space in that context.
So in the final commit i've moved the string to a single line, see it
attached below.
Ingo
--------------->
>From 55c395b47042e12d5c25aa07f271f56ffe44f793 Mon Sep 17 00:00:00 2001
From: Michael Tokarev <mjt@tls.msk.ru>
Date: Fri, 5 Dec 2008 14:42:20 +0300
Subject: [PATCH] x86: fix missing space in printk
Just come across this when booting on an old hw..
Looks somewhat ugly, that single missing space ;)
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/kernel/smpboot.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
index 7b10933..1a3c325 100644
--- a/arch/x86/kernel/smpboot.c
+++ b/arch/x86/kernel/smpboot.c
@@ -1086,8 +1086,10 @@ static int __init smp_sanity_check(unsigned max_cpus)
#endif
if (!physid_isset(hard_smp_processor_id(), phys_cpu_present_map)) {
- printk(KERN_WARNING "weird, boot CPU (#%d) not listed"
- "by the BIOS.\n", hard_smp_processor_id());
+ printk(KERN_WARNING
+ "weird, boot CPU (#%d) not listed by the BIOS.\n",
+ hard_smp_processor_id());
+
physid_set(hard_smp_processor_id(), phys_cpu_present_map);
}
next prev parent reply other threads:[~2008-12-05 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 11:42 Michael Tokarev
2008-12-05 12:10 ` Ingo Molnar [this message]
2008-12-05 12:47 ` Michael Tokarev
2008-12-05 13:01 ` Ingo Molnar
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=20081205121046.GA28662@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=x86@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
all inboxes | Powered by JetHome®