From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/urgent fixes for v3.5
Date: Wed, 23 May 2012 19:48:44 +0200 [thread overview]
Message-ID: <20120523174844.GA3373@gmail.com> (raw)
In-Reply-To: <4FBD1AC8.7020602@zytor.com>
* H. Peter Anvin <hpa@zytor.com> wrote:
> On 05/23/2012 10:07 AM, Linus Torvalds wrote:
> > On Wed, May 23, 2012 at 4:34 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >>
> >> Sasha Levin (1):
> >> x86, printk: Add missing KERN_CONT to NMI selftest
> >
> > Why? This seems to be garbage.
> >
>
> This was added to the urgent branch earlier (but it wasn't
> worth pushing late in rc) but apparently a more underlying bug
> was fixed in the meantime.
>
> It didn't seem worth removing since the KERN_CONT should
> really be there anyway.
I'm not sure it should be there: if there's no KERN_ prefix in a
printk, and the previous printk from this context did not end
with \n, then the KERN_CONT should be implicit.
KERN_CONT is really special, for rare cases where you want to
explicitly avoid the <> priority field or to construct it.
Or at least that's how I understand this area, it might have
been updated meanwhile - Linus?
Also, we can rebase the whole branch and get rid of this one and
of the merge commit it has.
Thanks,
Ingo
next prev parent reply other threads:[~2012-05-23 17:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 11:34 [GIT PULL] x86/urgent fixes for v3.5 Ingo Molnar
2012-05-23 17:07 ` Linus Torvalds
2012-05-23 17:13 ` H. Peter Anvin
2012-05-23 17:48 ` Ingo Molnar [this message]
2012-05-23 17:57 ` Linus Torvalds
2012-05-24 5:27 ` Ingo Molnar
2012-05-24 15:31 ` H. Peter Anvin
2012-05-24 15:44 ` Linus Torvalds
2012-05-24 15:54 ` Chen
2012-05-24 17:07 ` Ingo Molnar
2012-05-25 2:40 ` Chen
2012-05-30 7:23 ` Ingo Molnar
2012-05-24 15:48 ` Chen
2012-05-24 17:19 ` Joe Perches
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=20120523174844.GA3373@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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