RE: [RFC PATCH] [MTD] OneNAND: Error message printing and bad blockscan errors

[Artem Bityutskiy <dedekind@infradead.org>]

Hello Kyungmin,

On Mon, 2007-02-05 at 16:36 +0900, Kyungmin Park wrote:
> > What is the status of this?
> 
> I'm not determine how to handle this one.
> As your opinion, It is one approach which separate the wait function for
> normal and bbt.
> Basically, you want to see what is happen when error occurs. however it's
> not useless for normal users
> 
> Another approaches are adding new ioctl as "ERRORGETSTATS" or sysfs
> interface.
> The former is more simple and latter needs more works.

All we wanted is not to be silent in case of sever errors. We hit this
in practice, so the demand in the patch is quite practical.

If you do not want to print errors on scanning phase, looks fair enough,
just add an if there. But Adrian found out that there are more
difference between the wait functions in case of scanning and normal
operations - at least because they react on errors differently. It is a
good reason to have 2 separate function, what he did.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)