OneNAND: Always print error messages
Artem Bityutskiy
dedekind at infradead.org
Wed Jan 17 20:34:32 EST 2007
Hi Kyungmin,
On Wed, 2007-01-17 at 23:57 +0000, Kyungmin Park wrote:
Yes, simple solution is separate read oob from normal and scanning.
> I think is is easy because we can use state variable, FL_SCANNING
instead of FL_READING in bbt.
> I will try it.
>
I meant something like this:
if (error occured
if (!(we are scanning the flash && this is a read OOB error))
printk("error message");
I guess Adrian could just tweak his patch and re-submit.
--
Best regards,
Artem Bityutskiy
More information about the linux-mtd
mailing list