mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Andi Kleen" <andi@firstfloor.org>
Cc: "Pekka Enberg" <penberg@cs.helsinki.fi>,
	linux-kernel@vger.kernel.org,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Rob Landley" <rob@landley.net>
Subject: Re: [RFC/PATCH] printk: detect incomplete lines
Date: Tue, 13 May 2008 17:31:20 +0200	[thread overview]
Message-ID: <19f34abd0805130831w6887e797jdc5e636eee3a0137@mail.gmail.com> (raw)
In-Reply-To: <87ej86scdc.fsf@basil.nowhere.org>

On Tue, May 13, 2008 at 12:54 PM, Andi Kleen <andi@firstfloor.org> wrote:
> "Vegard Nossum" <vegard.nossum@gmail.com> writes:
>  >
>  > Iirc, KERN_CONT is mostly an annotation for the checkpatch script to
>  > suppress the warning about missing loglevel token.
>
>  Perhaps it should be fixed to contain some magic token that is
>  then detected by printk and handled appropiately? And then perhaps
>  employee some kernel janitors to add it everywhere?
>
>  I think that would be preferable over any heuristics as implemented
>  in your original patch because there might be a legitimate need to
>  get out non full line printks ASAP for debugging.

I'm sorry, I don't understand what you mean. My original patch does
not delay anything. My original patch simply inserts a newline before
the next printk() if the caller is different and the current line is
unterminated.

What would be the purpose of the magic token? Please explain.


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

  reply	other threads:[~2008-05-13 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 11:49 Vegard Nossum
2008-05-12 11:56 ` Pekka Enberg
2008-05-12 12:00   ` Vegard Nossum
2008-05-13 10:54     ` Andi Kleen
2008-05-13 15:31       ` Vegard Nossum [this message]
2008-05-12 15:35 ` 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=19f34abd0805130831w6887e797jdc5e636eee3a0137@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=rob@landley.net \
    /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®