From: Mike Crowe <mac@mcrowe.com>
To: linux-mips@linux-mips.org
Subject: [PATCH] MIPS: Add severity levels to printk statements during kernel setup.
Date: Fri, 25 Jul 2008 14:44:54 +0100 [thread overview]
Message-ID: <20080725134454.GA26225@mcrowe.com> (raw)
Signed-off-by: Mike Crowe <mac@mcrowe.com>
---
arch/mips/kernel/setup.c | 14 +++++++-------
1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c
index 8af8486..fcb12b9 100644
--- a/arch/mips/kernel/setup.c
+++ b/arch/mips/kernel/setup.c
@@ -78,7 +78,7 @@ void __init add_memory_region(phys_t start, phys_t size, long type)
/* Sanity check */
if (start + size < start) {
- printk("Trying to add an invalid memory region, skipped\n");
+ printk(KERN_WARNING "Trying to add an invalid memory region, skipped\n");
return;
}
@@ -92,7 +92,7 @@ void __init add_memory_region(phys_t start, phys_t size, long type)
}
if (x == BOOT_MEM_MAP_MAX) {
- printk("Ooops! Too many entries in the memory map!\n");
+ printk(KERN_ERR "Ooops! Too many entries in the memory map!\n");
return;
}
@@ -108,7 +108,7 @@ static void __init print_memory_map(void)
const int field = 2 * sizeof(unsigned long);
for (i = 0; i < boot_mem_map.nr_map; i++) {
- printk(" memory: %0*Lx @ %0*Lx ",
+ printk(KERN_INFO " memory: %0*Lx @ %0*Lx ",
field, (unsigned long long) boot_mem_map.map[i].size,
field, (unsigned long long) boot_mem_map.map[i].addr);
@@ -221,7 +221,7 @@ static void __init finalize_initrd(void)
goto disable;
}
if (__pa(initrd_end) > PFN_PHYS(max_low_pfn)) {
- printk("Initrd extends beyond end of memory");
+ printk(KERN_ERR "Initrd extends beyond end of memory");
goto disable;
}
@@ -232,7 +232,7 @@ static void __init finalize_initrd(void)
initrd_start, size);
return;
disable:
- printk(" - disabling initrd\n");
+ printk(KERN_ERR " - disabling initrd\n");
initrd_start = 0;
initrd_end = 0;
}
@@ -471,7 +471,7 @@ static void __init arch_mem_init(char **cmdline_p)
/* call board setup routine */
plat_mem_setup();
- printk("Determined physical RAM map:\n");
+ printk(KERN_INFO "Determined physical RAM map:\n");
print_memory_map();
strlcpy(command_line, arcs_cmdline, sizeof(command_line));
@@ -482,7 +482,7 @@ static void __init arch_mem_init(char **cmdline_p)
parse_early_param();
if (usermem) {
- printk("User-defined physical RAM map:\n");
+ printk(KERN_INFO "User-defined physical RAM map:\n");
print_memory_map();
}
--
1.5.6
next reply other threads:[~2008-07-25 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 13:44 Mike Crowe [this message]
2008-07-25 18:04 ` [PATCH] MIPS: Add severity levels to printk statements during kernel setup Geert Uytterhoeven
2008-07-26 12:59 ` Mike Crowe
2008-07-26 13:19 ` Geert Uytterhoeven
2008-07-28 12:12 ` [PATCH] MIPS: Convert printk statements during kernel setup to use severity levels Mike Crowe
2008-07-30 13:49 ` Ralf Baechle
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=20080725134454.GA26225@mcrowe.com \
--to=mac@mcrowe.com \
--cc=linux-mips@linux-mips.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