From: Joe Perches <joe@perches.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: mingo@kernel.org, levinsasha928@gmail.com,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86, printk: Add missing KERN_CONT to NMI selftest
Date: Mon, 21 May 2012 10:56:39 -0700 [thread overview]
Message-ID: <1337622999.13812.11.camel@joe2Laptop> (raw)
In-Reply-To: <4FBA7E95.5040101@zytor.com>
On Mon, 2012-05-21 at 10:42 -0700, H. Peter Anvin wrote:
> On 05/21/2012 10:29 AM, Joe Perches wrote:
> > I believe this change is no longer required.
> > Kay's printk modifications have been updated.
> > It's somewhat useful, but the commit message
> > but not the commit subject is untrue.
> Still, the KERN_CONT should be there.
True.
All the other printks in the same file
without KERN_ levels should be fixed too.
It might be better to fix them all at once.
$ git grep -w -n printk arch/x86/kernel/nmi_selftest.c|grep -v KERN_|grep '[^"]\\n'
arch/x86/kernel/nmi_selftest.c:146: printk("----------------\n");
arch/x86/kernel/nmi_selftest.c:147: printk("| NMI testsuite:\n");
arch/x86/kernel/nmi_selftest.c:148: printk("--------------------\n");
arch/x86/kernel/nmi_selftest.c:160: printk("--------------------\n");
arch/x86/kernel/nmi_selftest.c:161: printk("BUG: %3d unexpected failures (out of %3d) - debugging disabled! |\n",
arch/x86/kernel/nmi_selftest.c:163: printk("-----------------------------------------------------------------\n");
arch/x86/kernel/nmi_selftest.c:165: printk("--------------------\n");
arch/x86/kernel/nmi_selftest.c:166: printk("%3d out of %3d testcases failed, as expected. |\n",
arch/x86/kernel/nmi_selftest.c:168: printk("----------------------------------------------------\n");
arch/x86/kernel/nmi_selftest.c:170: printk("--------------------\n");
arch/x86/kernel/nmi_selftest.c:171: printk("All %3d testcases failed, as expected. |\n",
arch/x86/kernel/nmi_selftest.c:173: printk("----------------------------------------\n");
arch/x86/kernel/nmi_selftest.c:175: printk("--------------------\n");
arch/x86/kernel/nmi_selftest.c:176: printk("Good, all %3d testcases passed! |\n",
arch/x86/kernel/nmi_selftest.c:178: printk("---------------------------------\n");
There are a couple hundred more in arch/x86.
$ git grep -w printk arch/x86/|grep -v KERN_|wc -l
203
next prev parent reply other threads:[~2012-05-21 17:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 15:56 [PATCH 1/4] mm: add missing KERN_CONT to free_area_init_nodes Sasha Levin
2012-05-08 15:56 ` [PATCH 2/4] locking: add KERN_CONT when needed to self test Sasha Levin
2012-05-08 15:56 ` [PATCH 3/4] x86, NMI: add missing KERN_CONT to NMI selftest Sasha Levin
2012-05-21 17:25 ` [tip:x86/urgent] x86, printk: Add " tip-bot for Sasha Levin
2012-05-21 17:29 ` Joe Perches
2012-05-21 17:42 ` H. Peter Anvin
2012-05-21 17:56 ` Joe Perches [this message]
2012-05-21 17:57 ` H. Peter Anvin
2012-05-22 2:49 ` [PATCH 1/2] x86: asm: Add KERN_<LEVEL> to printks Joe Perches
2012-05-22 2:50 ` [PATCH 2/2] x86: Add KERN_<LEVEL> to bare printks, convert printks to pr_<level> Joe Perches
2012-06-06 15:03 ` [tip:x86/debug] x86/debug: " tip-bot for Joe Perches
2012-05-08 15:56 ` [PATCH 4/4] ISDN: add missing KERN_CONT Sasha Levin
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=1337622999.13812.11.camel@joe2Laptop \
--to=joe@perches.com \
--cc=hpa@zytor.com \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).