From: Mark Lord <lkml@rtr.ca>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix bytecount result from printk()
Date: Thu, 01 Dec 2005 11:25:51 -0500 [thread overview]
Message-ID: <438F240F.2020300@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.64.0512010808240.3099@g5.osdl.org>
Linus Torvalds wrote:
>
> On Thu, 1 Dec 2005, Mark Lord wrote:
>
>>On a related note, WHY does the LOG LEVEL format <6> not get
>>interpreted correctly for the first printk() after an oops report?
>
> It never gets interpreted except at the behinning of a line. Sounds like
> the oops report perhaps prints a " " without a newline or something at the
> end, so that the next message after that isn't a new line?
The oops report always ends with a simple newline: printk("\n");
next prev parent reply other threads:[~2005-12-01 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 15:55 [PATCH] Fix bytecount result from printk() Mark Lord
2005-12-01 16:09 ` Linus Torvalds
2005-12-01 16:25 ` Mark Lord [this message]
2005-12-01 17:57 ` Dave Jones
2005-12-01 20:15 ` David S. Miller
2005-12-02 1:23 ` Andi Kleen
2005-12-01 21:09 ` Mark Lord
2005-12-01 21:16 ` Andi Kleen
2005-12-02 2:04 ` Andrew Morton
2005-12-02 2:22 ` Mark Lord
2005-12-01 20:14 ` David S. Miller
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=438F240F.2020300@rtr.ca \
--to=lkml@rtr.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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