From: Jeff Dike <jdike@addtoit.com>
To: Rob Landley <rob@landley.net>
Cc: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [PATCH] make quiet suppress parse_chan_pair boot messages
Date: Fri, 9 May 2008 11:22:17 -0400 [thread overview]
Message-ID: <20080509152217.GF10169@c2.user-mode-linux.org> (raw)
In-Reply-To: <200805031518.11029.rob@landley.net>
On Sat, May 03, 2008 at 03:18:10PM -0500, Rob Landley wrote:
> I usually use UML as a better fakeroot, meaning I run it with a command line
> like "rootfstype=hostfs rw quiet init=/path/to/some_shell_script.sh". In this
> context, filling the screen with parse_chan_pair error messages which don't
> actually hurt anything defeats the purpose of "quiet".
>
> The patch turns several KERN_ERR into KERN_WARNING. While I was there, I
> merged the redundant printk() statements into a function, and added one "else"
> after a test-for-null that did a printk but didn't do a continue.
Looks reasonable.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2008-05-09 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 20:18 [uml-devel] [PATCH] make quiet suppress parse_chan_pair boot messages Rob Landley
2008-05-04 20:48 ` Geert Uytterhoeven
2008-05-09 15:22 ` Jeff Dike [this message]
2008-05-17 19:08 ` Rob Landley
2008-05-19 16:12 ` [uml-devel] [PATCH] make quiet suppress parse_chan_pair boot?messages Jeff Dike
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=20080509152217.GF10169@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=rob@landley.net \
--cc=user-mode-linux-devel@lists.sourceforge.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