From: Nick Andrew <nick@nick-andrew.net>
To: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] fs: fix warning message with inserting a single space
Date: Mon, 8 Dec 2008 23:35:17 +1100 [thread overview]
Message-ID: <20081208123517.GA3892@mail.local.tull.net> (raw)
In-Reply-To: <1228737252-31948-1-git-send-email-Hiroshi.DOYU@nokia.com>
On Mon, Dec 08, 2008 at 01:54:12PM +0200, Hiroshi DOYU wrote:
> - printk(KERN_WARNING "%s: %s passed in a files array"
> + printk(KERN_WARNING "%s: %s passed in a files array "
> "with an index of 1!\n", __func__,
> s->s_type->name);
Yep. These look like the same kind of thing:
arch/powerpc/platforms/cell/iommu.c +1109
pr_debug("iommu: hash window doesn't fit in"
"real DMA window\n");
arch/powerpc/platforms/cell/spider-pci.c +138
pr_err("SPIDERPCI-IOWA:"
"Can't allocate struct spiderpci_iowa_private");
(space after a colon?)
arch/x86/kernel/microcode_intel.c +374
printk(KERN_ERR "microcode: error!"
"Bad data in microcode data file\n");
arch/x86/kernel/microcode_amd.c +411
printk(KERN_WARNING "microcode: AMD microcode update via /dev/cpu/microcode"
"is not supported\n");
arch/x86/kernel/pci-dma.c +303
printk(KERN_INFO "PCI: VIA PCI bridge detected."
"Disabling DAC.\n");
arch/x86/kernel/smpboot.c +412
printk(KERN_WARNING "WARNING: SMP operation may be unreliable"
"with B stepping processors.\n");
arch/x86/kernel/smpboot.c +420
printk(KERN_INFO "WARNING: This combination of AMD"
"processors is not suitable for SMP.\n");
arch/x86/kernel/smpboot.c +1089
printk(KERN_WARNING "weird, boot CPU (#%d) not listed"
"by the BIOS.\n", hard_smp_processor_id());
arch/x86/kernel/smpboot.c +1127
printk(KERN_ERR "... forcing use of dummy APIC emulation."
"(tell your hw vendor)\n");
arch/x86/mm/init_32.c +668
printk(KERN_WARNING "Warning only 4GB will be used."
"Use a HIGHMEM64G enabled kernel.\n");
arch/arm/common/dmabounce.c +510
"Never registered with dmabounce but attempting"
"to unregister!\n");
arch/arm/plat-omap/dma.c +1843
printk(KERN_WARNING "IRQ %04x for non-allocated DMA"
"channel %d\n", status, ch);
arch/arm/plat-omap/mcbsp.c +874
dev_err(&pdev->dev, "McBSP device initialized without"
"platform data\n");
arch/arm/mach-s3c2412/mach-jive.c +255
printk(KERN_ERR "Unknown mtd set %ld specified,"
"using default.", set);
arch/arm/mach-pxa/trizeps4.c +354
printk(KERN_ERR "trizeps4_mci_init: MMC/SD: can't request"
"MMC card detect IRQ\n");
arch/arm/mach-pxa/mioa701.c +651
printk(KERN_CRIT "Unregistering mioa701 suspend will hang next"
"resume !!!\n");
arch/ia64/sn/kernel/io_common.c +354
printk(KERN_WARNING "on node %d but only %d nodes online."
"Association set to undetermined.\n",
arch/ia64/kernel/kprobes.c +249
printk(KERN_WARNING "Kprobes on IP-Relative"
"Predict is not supported\n");
Nick.
next prev parent reply other threads:[~2008-12-08 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 11:54 Hiroshi DOYU
2008-12-08 12:35 ` Nick Andrew [this message]
2008-12-08 13:16 ` Artem Bityutskiy
2008-12-08 13:22 ` Artem Bityutskiy
2008-12-08 13:24 ` Oliver Neukum
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=20081208123517.GA3892@mail.local.tull.net \
--to=nick@nick-andrew.net \
--cc=Hiroshi.DOYU@nokia.com \
--cc=linux-kernel@vger.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®