From: Masami Hiramatsu <mhiramat@kernel.org>
To: Jeff Dike <jdike@addtoit.com>, Richard Weinberger <richard@nod.at>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH v2 0/6] um: Output messages to stderr and support quiet option
Date: Mon, 8 May 2017 15:15:21 +0900 [thread overview]
Message-ID: <149422411127.11101.13017249012576512464.stgit@devbox> (raw)
Hello,
Here is version 2 of um-quiet series.
This series fixes some boot time printf output to stderr
by adding os_info() and os_warn(). The information-level
messages via os_info() are suppressed when "quiet" kernel
option is specified.
Also the last one allows user to pass "console=" option
to kernel.
Note that the output of --help and --version are still
sent to stdout since they are intentionally shown by
the user.
Changes from v1:
- Introduce os_info() and os_warn() to replace most of
printf() instead of reusing non_fatal().
- Replace fprintf(stderr, ...) with os_warn() for error
messages.
Thank you,
---
Masami Hiramatsu (6):
um: Use printk instead of printf in make_uml_dir
um: Add os_info() for pre-boot information messages
um: Use os_info for the messages on normal path
um: Add os_warn() for pre-boot warning/error messages
um: Use os_warn to print out pre-boot warning/error messages
um: console: Ignore console= option
arch/um/drivers/stdio_console.c | 3 +++
arch/um/include/shared/os.h | 4 ++++
arch/um/kernel/physmem.c | 10 +++++-----
arch/um/kernel/um_arch.c | 16 +++++++++-------
arch/um/kernel/umid.c | 4 ++--
arch/um/os-Linux/execvp.c | 2 +-
arch/um/os-Linux/main.c | 9 ++++-----
arch/um/os-Linux/mem.c | 28 ++++++++++++++--------------
arch/um/os-Linux/start_up.c | 28 +++++++++++++++-------------
arch/um/os-Linux/umid.c | 19 +++++++++++--------
arch/um/os-Linux/util.c | 34 ++++++++++++++++++++++++++++++++++
11 files changed, 102 insertions(+), 55 deletions(-)
--
Masami Hiramatsu <mhiramat@kernel.org>
next reply other threads:[~2017-05-08 6:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 6:15 Masami Hiramatsu [this message]
2017-05-08 6:16 ` [RFC PATCH v2 1/6] um: Use printk instead of printf in make_uml_dir Masami Hiramatsu
2017-05-08 6:17 ` [RFC PATCH v2 2/6] um: Add os_info() for pre-boot information messages Masami Hiramatsu
2017-05-08 6:18 ` [RFC PATCH v2 3/6] um: Use os_info for the messages on normal path Masami Hiramatsu
2017-05-08 6:20 ` [RFC PATCH v2 4/6] um: Add os_warn() for pre-boot warning/error messages Masami Hiramatsu
2017-05-08 6:21 ` [RFC PATCH v2 5/6] um: Use os_warn to print out " Masami Hiramatsu
2017-05-08 6:22 ` [RFC PATCH v2 6/6] um: console: Ignore console= option Masami Hiramatsu
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=149422411127.11101.13017249012576512464.stgit@devbox \
--to=mhiramat@kernel.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--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