From: Brian Norris <computersforpeace@gmail.com>
To: Josh Wu <josh.wu@atmel.com>
Cc: derosier@gmail.com, linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mtd: atmel_nand: return max bitflips in all sectors in pmecc_correction()
Date: Tue, 20 Jan 2015 12:44:42 -0800 [thread overview]
Message-ID: <20150120204442.GQ9759@ld-irv-0074> (raw)
In-Reply-To: <1421207446-16973-1-git-send-email-josh.wu@atmel.com>
On Wed, Jan 14, 2015 at 11:50:46AM +0800, Josh Wu wrote:
> atmel_nand_pmecc_read_page() will return the total bitflips in this
> page. This is incorrect.
>
> As one nand page includes multiple ecc sectors, that will cause the
> returned total bitflips exceed ecc capablity.
>
> So this patch will make pmecc_correct() return the max bitflips of all
> sectors in the page. That also makes atmel_nand_pmecc_read_page() return
> the max bitflips.
>
> Signed-off-by: Josh Wu <josh.wu@atmel.com>
Pushed to l2-mtd.git. Thanks.
Brian
prev parent reply other threads:[~2015-01-20 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 3:50 [PATCH] mtd: atmel_nand: return max bitflips in all sectors in pmecc_correction() Josh Wu
2015-01-20 20:44 ` Brian Norris [this message]
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=20150120204442.GQ9759@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=derosier@gmail.com \
--cc=josh.wu@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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