[PATCH] MTD: OneNAND: minor print fix
Artem Bityutskiy
dedekind at infradead.org
Thu Sep 20 10:17:34 EDT 2007
>From 34fdb6b9c912f0be9d92f05a0dfeb47f9145b5cc Mon Sep 17 00:00:00 2001
From: Artem Bityutskiy <Artem.Bityutskiy at nokia.com>
Date: Thu, 20 Sep 2007 17:13:34 +0300
Subject: [PATCH] MTD: OneNAND: minor print fix
Use the same printk level when printing version information.
There is no reason to print it with KERN_DEBUG when the previous
message was printed with KERN_INFO.
And it is really interesting information to print because it gives
you exact part number and the operating frequency (54MHz, 66MHz, etc).
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy at nokia.com>
---
drivers/mtd/onenand/onenand_base.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mtd/onenand/onenand_base.c b/drivers/mtd/onenand/onenand_base.c
index 0a18528..bb01369 100644
--- a/drivers/mtd/onenand/onenand_base.c
+++ b/drivers/mtd/onenand/onenand_base.c
@@ -2148,7 +2148,7 @@ static void onenand_print_device_info(int device, int version)
(16 << density),
vcc ? "2.65/3.3" : "1.8",
device);
- printk(KERN_DEBUG "OneNAND version = 0x%04x\n", version);
+ printk(KERN_INFO "OneNAND version 0x%04x\n", version);
}
static const struct onenand_manufacturers onenand_manuf_ids[] = {
--
1.5.2.2
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
More information about the linux-mtd
mailing list