public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Huang Ying <ying.huang@intel.com>
Cc: William Douglas <william.r.douglas@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Printk mulitple line message support
Date: Mon, 14 Nov 2011 19:41:08 -0800	[thread overview]
Message-ID: <1321328468.18124.2.camel@Joe-Laptop> (raw)
In-Reply-To: <1321325960.13860.75.camel@yhuang-dev>

On Tue, 2011-11-15 at 10:59 +0800, Huang Ying wrote:
> For multiple part in one line.  I think the better solution may be to
> assemble them in a line buffer before real output to console to avoid
> interleaving.  Do you think so?

Hard to say yes for sure.  Immediacy has some value.

There are some downsides to preassembly in memory
constrained systems.

On the other hand, most uses of pr_cont don't create
very long lines.


  reply	other threads:[~2011-11-15  3:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14  6:58 Printk mulitple line message support Huang Ying
2011-11-14 14:40 ` Joe Perches
2011-11-14 18:20   ` Bruno Prémont
2011-11-15  0:18     ` Joe Perches
2011-11-15  0:58     ` Huang Ying
2011-11-15  0:50   ` Huang Ying
2011-11-15  1:18     ` Joe Perches
2011-11-15  1:52       ` Huang Ying
2011-11-15  2:30         ` Joe Perches
2011-11-15  2:59           ` Huang Ying
2011-11-15  3:41             ` Joe Perches [this message]
2011-11-16  0:43               ` Huang Ying
2011-11-16  0:45           ` Huang Ying
2011-11-16  0:54             ` Joe Perches
2011-11-16  0:29       ` Valdis.Kletnieks
2011-11-16  0:34         ` 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=1321328468.18124.2.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=william.r.douglas@gmail.com \
    --cc=ying.huang@intel.com \
    /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