OneNAND: Always print error messages

[Kyungmin Park]

Hi Artem,

> Yeah, it indeed makes few sense to print out error message if we meet a
> bad block. But being silent when errors occur is bad as well.

I agree

> > I'm not sure how to handle error message, especillay at onenand_wait().
> > controller error is very important but it's too verbose at boot time.

> We can avoid doing this if (1) we cannot read OOB (1) and we are
> scanning (2). In other cases we print the error message. Comments?

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.

Thank you,
Kyungmin Park