public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@sw.ru>
To: Ingo Molnar <mingo@elte.hu>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	akpm@osdl.org, linux-kernel@vger.kernel.org, devel@openvz.org
Subject: Re: [PATCH] Bogus KERN_ALERT on oops
Date: Wed, 24 Oct 2007 15:39:09 +0400	[thread overview]
Message-ID: <20071024113909.GA6214@localhost.sw.ru> (raw)
In-Reply-To: <20071024103318.GB18741@elte.hu>

On Wed, Oct 24, 2007 at 12:33:18PM +0200, Ingo Molnar wrote:
> 
> * Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> 
> > > -                       printk(KERN_ALERT "*pde = %016Lx ", page);
> > > +                       printk("*pde = %016Lx ", page);
> > 
> > Use the new KERN_CONT annotation here?
> 
> indeed - i changed the patch to do that.

Might as well change comment around KERN_CONT -- for starters it lied
about "early bootup" phase since day one.

Proposed text:

	/*
	 * Annotation for a "continued" line of log printout (only done
	 * after a line that had no enclosing \n).
	 *
	 * Introduced because checkpatch.pl couldn't be arsed to learn C
	 * and distinguish continued printk() from the one that starts
	 * new line.
	 *
	 * Caveat #1: Empty string-literal, so compiler can't check for
	 *            KERN_CONT misuse.
	 * Caveat #2: Empty string-literal, so it can't be used in
	 *            printk(var); situations.
	 * Caveat #3: takes characters on the screen, so code is harder
	 *            to read.
	 * Caveat #4: checkpatch.pl doesn't know C, so it can't check
	 *            for KERN_CONT misuse, anyway.
	 */


  reply	other threads:[~2007-10-24 11:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 11:57 [PATCH] Bogus KERN_ALERT on oops Alexey Dobriyan
2007-10-22 13:06 ` Pekka Enberg
2007-10-24 10:33   ` Ingo Molnar
2007-10-24 11:39     ` Alexey Dobriyan [this message]
2007-10-24 10:32 ` 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=20071024113909.GA6214@localhost.sw.ru \
    --to=adobriyan@sw.ru \
    --cc=akpm@osdl.org \
    --cc=devel@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    /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