From: Ingo Molnar <mingo@elte.hu>
To: Nick Andrew <nick@nick-andrew.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
joe@perches.com
Subject: Re: [PATCH 2/2] printk: Remember the message level for multi-line output
Date: Mon, 14 Apr 2008 10:03:51 +0200 [thread overview]
Message-ID: <20080414080351.GL16163@elte.hu> (raw)
In-Reply-To: <20080413122735.31769.17716.stgit@marcab.local.tull.net>
* Nick Andrew <nick@nick-andrew.net> wrote:
> printk: Remember the message level for multi-line output
>
> printk(KERN_ALERT "Danger Will Robinson!\nAlien Approaching!\n");
>
> At present this will result in one message at ALERT level and one at
> the current default message loglevel (e.g. WARNING). This is
> non-intuitive.
>
> Modify vprintk() to remember the message loglevel each time it is
> specified and use it for subsequent lines of output which do not
> specify one, within the same call to printk.
i've applied this too for testing.
but multi-line strings are a bit unclean i think: each message line
should have its separate printk.
will your patch leave the behavior of multiple calls to printk alone?
I.e. if i do:
printk(KERN_ALERT "Danger Will Robinson!\n");
printk("Alien Approaching!\n");
then we'll still get a KERN_ALERT plus a default printk, right? In that
case my earlier observation about this patch is moot and i guess it's
fine to do this.
Ingo
next prev parent reply other threads:[~2008-04-14 8:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 11:53 [PATCH 1/2] printk: Refactor processing of line severity tokens Nick Andrew
2008-04-13 11:54 ` [PATCH 2/2] printk: Remember the message level for multi-line output Nick Andrew
2008-04-13 12:26 ` [PATCH 1/2] printk: Refactor processing of line severity tokens Nick Andrew
2008-04-14 7:58 ` Ingo Molnar
2008-04-13 12:27 ` [PATCH 2/2] printk: Remember the message level for multi-line output Nick Andrew
2008-04-14 8:03 ` Ingo Molnar [this message]
2008-04-14 10:12 ` Nick Andrew
2008-04-14 10:26 ` Ingo Molnar
2008-04-14 11:03 ` Nick Andrew
2008-04-14 11:43 ` Johannes Weiner
2008-04-14 12:21 ` 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=20080414080351.GL16163@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@nick-andrew.net \
--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
Powered by JetHome