mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Ingo Molnar <mingo@elte.hu>
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, 05 Dec 2008 15:47:29 +0300	[thread overview]
Message-ID: <493922E1.4050501@msgid.tls.msk.ru> (raw)
In-Reply-To: <20081205121046.GA28662@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]

Ingo Molnar wrote:
> * 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.

Oh well.  Thanks.  There's another very similar thing in
arch/x86/kernel/pci-dma.c, via_no_dac() (attached).

By the way, where such tiny/trivial things should go?

Thanks!

/mjt

[-- Attachment #2: viadac.diff --]
[-- Type: text/x-patch, Size: 473 bytes --]

--- a/arch/x86/kernel/pci-dma.c	2008-10-10 02:13:53 +0400
+++ b/arch/x86/kernel/pci-dma.c	2008-12-05 15:45:56 +0300
@@ -409,8 +409,8 @@ fs_initcall(pci_iommu_init);
 static __devinit void via_no_dac(struct pci_dev *dev)
 {
 	if ((dev->class >> 8) == PCI_CLASS_BRIDGE_PCI && forbid_dac == 0) {
-		printk(KERN_INFO "PCI: VIA PCI bridge detected."
-				 "Disabling DAC.\n");
+		printk(KERN_INFO
+			"PCI: VIA PCI bridge detected. Disabling DAC.\n");
 		forbid_dac = 1;
 	}
 }

  reply	other threads:[~2008-12-05 12:47 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
2008-12-05 12:47   ` Michael Tokarev [this message]
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=493922E1.4050501@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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®