[<prev] [next>] [day] [month] [year] [list]
Message-Id: <200902241510.24993.david-b@pacbell.net>
Date: Tue, 24 Feb 2009 15:10:24 -0800
From: David Brownell <david-b@...bell.net>
To: Linux MTD <linux-mtd@...ts.infradead.org>
Cc: lkml <linux-kernel@...r.kernel.org>
Subject: [patch/RESEND 2.6.29-rc3] NAND: fix broken debug messages (v2)
From: David Brownell <dbrownell@...rs.sourceforge.net>
Fix incorrect debug messages (*write* not read); someone
committed some cut'n'paste bugs. There might be more,
I only noticed these since I was looking for nand_read
usage and landed in some very wrong functions.
IMO all MTD debugging message framework is goofed, anyway.
It uses "DEBUG" in a way that's incompatible with usage
most everywhere else in the kernel, and which prevents
normal pr_dbg() and dev_dbg() calls from working right.
Signed-off-by: David Brownell <dbrownell@...rs.sourceforge.net>
---
Fix a goofed string.
drivers/mtd/nand/nand_base.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--- a/drivers/mtd/nand/nand_base.c
+++ b/drivers/mtd/nand/nand_base.c
@@ -1948,7 +1948,7 @@ static int nand_do_write_oob(struct mtd_
}
if (unlikely(ops->ooboffs >= len)) {
- DEBUG(MTD_DEBUG_LEVEL0, "nand_read_oob: "
+ DEBUG(MTD_DEBUG_LEVEL0, "nand_do_write_oob: "
"Attempt to start write outside oob\n");
return -EINVAL;
}
@@ -1958,7 +1958,7 @@ static int nand_do_write_oob(struct mtd_
ops->ooboffs + ops->ooblen >
((mtd->size >> chip->page_shift) -
(to >> chip->page_shift)) * len)) {
- DEBUG(MTD_DEBUG_LEVEL0, "nand_read_oob: "
+ DEBUG(MTD_DEBUG_LEVEL0, "nand_do_write_oob: "
"Attempt write beyond end of device\n");
return -EINVAL;
}
@@ -2014,8 +2014,8 @@ static int nand_write_oob(struct mtd_inf
/* Do not allow writes past end of device */
if (ops->datbuf && (to + ops->len) > mtd->size) {
- DEBUG(MTD_DEBUG_LEVEL0, "nand_read_oob: "
- "Attempt read beyond end of device\n");
+ DEBUG(MTD_DEBUG_LEVEL0, "nand_write_oob: "
+ "Attempt write beyond end of device\n");
return -EINVAL;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists