From: "H. Peter Anvin" <hpa@zytor.com>
To: Joe Perches <joe@perches.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:42:45 -0700 [thread overview]
Message-ID: <4FBA7E95.5040101@zytor.com> (raw)
In-Reply-To: <1337621394.13812.2.camel@joe2Laptop>
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.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-05-21 17:43 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 [this message]
2012-05-21 17:56 ` Joe Perches
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=4FBA7E95.5040101@zytor.com \
--to=hpa@zytor.com \
--cc=joe@perches.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.