From: Mike Dunn <mikedunn@newsguy.com>
To: Peter Barada <peter.barada@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/3] MTD: Change meaning of -EUCLEAN return code on reads
Date: Sat, 17 Mar 2012 14:10:26 -0700 [thread overview]
Message-ID: <4F64FDC2.9090400@newsguy.com> (raw)
In-Reply-To: <4F63C571.4000400@gmail.com>
On 03/16/2012 03:57 PM, Peter Barada wrote:
> On 03/16/2012 05:54 PM, Shmulik Ladkani wrote:
> I think the indication from MTD should be the worst case found in
> all the ECC steps...
Yes, that's the consensus. Some of us are just a litle slow :)
next prev parent reply other threads:[~2012-03-17 21:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 17:25 [PATCH 0/3] MTD: Change meaning of -EUCLEAN return code on reads Mike Dunn
2012-03-15 17:25 ` [PATCH 1/3] MTD: expose ecc_strength through sysfs Mike Dunn
2012-03-15 17:25 ` [PATCH 2/3] MTD: bitflip_threshold added to mtd_info and sysfs Mike Dunn
2012-03-16 16:31 ` Ivan Djelic
2012-03-15 17:25 ` [PATCH 3/3] MTD: drivers return max_bitflips, mtd returns -EUCLEAN Mike Dunn
2012-03-16 11:19 ` [PATCH 0/3] MTD: Change meaning of -EUCLEAN return code on reads Ivan Djelic
2012-03-16 12:49 ` Artem Bityutskiy
2012-03-16 16:30 ` Mike Dunn
2012-03-16 16:25 ` Mike Dunn
2012-03-16 18:43 ` Ivan Djelic
2012-03-17 20:18 ` Mike Dunn
2012-03-18 8:00 ` Shmulik Ladkani
2012-03-19 8:50 ` Matthieu CASTET
2012-03-19 9:29 ` Shmulik Ladkani
2012-03-19 19:09 ` Mike Dunn
[not found] ` <20120319211835.1073a491@halley>
2012-03-20 1:27 ` Mike Dunn
2012-03-30 14:21 ` Artem Bityutskiy
2012-03-31 2:03 ` Mike Dunn
2012-03-30 14:16 ` Artem Bityutskiy
2012-03-31 1:23 ` Mike Dunn
2012-03-30 14:19 ` Artem Bityutskiy
2012-03-16 21:54 ` Shmulik Ladkani
2012-03-16 22:57 ` Peter Barada
2012-03-17 21:10 ` Mike Dunn [this message]
2012-03-17 20:50 ` Mike Dunn
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=4F64FDC2.9090400@newsguy.com \
--to=mikedunn@newsguy.com \
--cc=linux-mtd@lists.infradead.org \
--cc=peter.barada@gmail.com \
/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