From: Mike Dunn <mikedunn@newsguy.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2 0/7] mtd: Change meaning of -EUCLEAN return code on reads
Date: Mon, 07 May 2012 09:20:27 -0700 [thread overview]
Message-ID: <4FA7F64B.3070003@newsguy.com> (raw)
In-Reply-To: <1336210990.2027.2.camel@koala>
On 05/05/2012 02:43 AM, Artem Bityutskiy wrote:
> On Wed, 2012-04-25 at 12:06 -0700, Mike Dunn wrote:
>> This v2 of this set includes the following changes:
>> - [Patch 4/7]: Propagate bitflip_threshold from master to slave partition.
>> - [Patch 5/7]: Zero out max_bitflips outside of if-block in fsl_ifc_nand.
>> - [Patch 6/7]: Simplify ecc strength sanity check.
>
> Would you please do one more thing - create a piece of documentation
> about this feature at the mtd web site.
OK. Please give me a few days to get to this.
Thanks,
Mike
next prev parent reply other threads:[~2012-05-07 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 19:06 [PATCH v2 0/7] mtd: Change meaning of -EUCLEAN return code on reads Mike Dunn
2012-04-25 19:06 ` [PATCH v2 1/7] mtd: ecc_strength is at ecc step granularity Mike Dunn
2012-04-25 19:06 ` [PATCH 2/7] mtd: nand: fix incorrect ecc strength values Mike Dunn
2012-04-25 19:06 ` [PATCH v2 3/7] mtd: expose ecc_strength through sysfs Mike Dunn
2012-04-25 19:06 ` [PATCH v2 4/7] mtd: bitflip_threshold added to mtd_info and sysfs Mike Dunn
2012-04-25 19:06 ` [PATCH v2 5/7] mtd: nand: read_page() returns max_bitflips Mike Dunn
2012-04-25 19:06 ` [PATCH v2 6/7] mtd: nand: add sanity check of ecc strength to nand_scan_tail() Mike Dunn
2012-05-02 6:17 ` Brian Norris
2012-04-25 19:06 ` [PATCH v2 7/7] mtd: driver _read() returns max_bitflips; mtd_read() returns -EUCLEAN Mike Dunn
2012-05-05 9:43 ` [PATCH v2 0/7] mtd: Change meaning of -EUCLEAN return code on reads Artem Bityutskiy
2012-05-07 16:20 ` Mike Dunn [this message]
2012-05-09 16:49 ` Mike Dunn
2012-05-09 16:54 ` Artem Bityutskiy
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=4FA7F64B.3070003@newsguy.com \
--to=mikedunn@newsguy.com \
--cc=dedekind1@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.