From: Kyungmin Park <kyungmin.park@samsung.com>
To: Adrian Hunter <ext-adrian.hunter@nokia.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: OneNAND: Always print error messages
Date: Fri, 12 Jan 2007 06:48:54 +0000 (GMT) [thread overview]
Message-ID: <929664.73441168584534274.JavaMail.weblogic@ep_ml28> (raw)
Hi Adrian,
I think it's too verbose.
As you know, nand flash has several initial bad blocks.
Maybe many uses don't like to see the some error message at boot time.
At least, onenand_wait(), onenand_do_read_oob() have to change from KERN_ERR to KERN_DEBUG
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.
Thank you,
Kyungmin Park
next reply other threads:[~2007-01-12 6:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 6:48 Kyungmin Park [this message]
2007-01-17 23:14 ` OneNAND: Always print error messages Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2007-01-17 23:57 Kyungmin Park
2007-01-18 1:34 ` Artem Bityutskiy
2007-01-18 16:24 ` Adrian Hunter
2007-01-19 7:14 Kyungmin Park
2007-01-19 8:02 ` Adrian Hunter
2007-01-19 8:21 Kyungmin Park
2007-01-19 8:58 ` Adrian Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=929664.73441168584534274.JavaMail.weblogic@ep_ml28 \
--to=kyungmin.park@samsung.com \
--cc=ext-adrian.hunter@nokia.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox