From: Andi Kleen <ak@muc.de>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.6-mm] Make i386 boot not so chatty
Date: Fri, 21 May 2004 12:29:05 +0200 [thread overview]
Message-ID: <m3vfiq3wge.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1Yaiz-33L-1@gated-at.bofh.it> (Zwane Mwaikambo's message of "Fri, 21 May 2004 07:00:07 +0200")
Zwane Mwaikambo <zwane@arm.linux.org.uk> writes:
> This patch silences the default i386 boot by putting a lot of development
> related printks under KERN_DEBUG loglevel, allowing the normal chatty mode
> to be turned on by using the 'debug' kernel parameter. I have avoided
> changing files which have external development repositories, like cpufreq and ACPI.
How about this much simpler patch?
-Andi
diff -u linux/kernel/printk.c-o linux/kernel/printk.c
--- linux/kernel/printk.c-o 2004-05-18 10:55:53.000000000 +0200
+++ linux/kernel/printk.c 2004-05-21 12:28:05.000000000 +0200
@@ -37,7 +37,7 @@
#define __LOG_BUF_LEN (1 << CONFIG_LOG_BUF_SHIFT)
/* printk's without a loglevel use this.. */
-#define DEFAULT_MESSAGE_LOGLEVEL 4 /* KERN_WARNING */
+#define DEFAULT_MESSAGE_LOGLEVEL 6 /* KERN_INFO */
/* We show everything that is MORE important than this.. */
#define MINIMUM_CONSOLE_LOGLEVEL 1 /* Minimum loglevel we let people use */
next parent reply other threads:[~2004-05-21 23:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1Yaiz-33L-1@gated-at.bofh.it>
2004-05-21 10:29 ` Andi Kleen [this message]
2004-05-21 15:13 ` [PATCH][2.6-mm] Make i386 boot not so chatty Zwane Mwaikambo
2004-05-21 4:46 Zwane Mwaikambo
2004-05-21 5:06 ` Zwane Mwaikambo
2004-05-21 12:10 ` Dave Jones
2004-05-21 15:19 ` Zwane Mwaikambo
2004-05-21 6:40 ` Andrew Morton
2004-05-21 15:14 ` Zwane Mwaikambo
2004-05-22 12:01 ` Ed Tomlinson
2004-05-24 15:54 ` Randy.Dunlap
2004-05-22 14:43 ` Bill Davidsen
2004-05-24 10:12 ` Pavel Machek
2004-05-27 19:39 ` Miquel van Smoorenburg
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=m3vfiq3wge.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.